XRP Ledger developers released xrpld version 3.3.0 on Aug. 6, adding code for privacy, atomic-batch transactions, delegated permissions and sponsored fees. None of the features are live yet — each still needs validator approval through the network's amendment process.
XRP Ledger developers released xrpld version 3.3.0 on Aug. 6, moving several protocol changes closer to possible mainnet activation. The GitHub release confirms work on ConfidentialTransfer, BatchV1_1, Sponsor and DynamicMPT, alongside fixes and other protocol changes, but the software release itself does not activate those features on the network.
Privacy and atomic transactions move toward a vote
ConfidentialTransfer is designed to add privacy for Multi-Purpose Tokens. The amendment uses cryptography to shield individual balances and transfer amounts while preserving mechanisms that let authorized parties, including issuers or auditors, verify information needed for compliance. Because the feature still requires amendment activation, private MPT transfers should not yet be described as active on the XRPL mainnet.
BatchV1_1 lets up to eight operations be combined into a single package that executes atomically, so either everything goes through together or nothing does. XRPL Foundation representative Vet said this opens the door to secure, trustless swaps and professional over-the-counter trading, according to U.Today.
Revised features follow earlier security findings
Batch has a troubled history. An earlier version was disabled before mainnet activation after a security issue was found in its transaction-signing logic, and the XRPL Foundation moved to BatchV1_1 as the corrected replacement. Permission Delegation followed a similar path: XRPL disclosed in September 2025 that a bug in the earlier amendment could have let an unauthorized transaction charge fees to another account, so validators were advised to vote no and the feature never activated. PermissionDelegationV1_1, its replacement, lets an account grant defined transaction permissions without handing over its main private key.
Sponsor and DynamicMPT target institutional users
Sponsor, based on the XLS-68 standard, would let another account cover transaction fees or reserve requirements while the user keeps control of the account and keys, potentially letting apps onboard users without requiring them to acquire XRP first. DynamicMPT would let token issuers designate selected properties as mutable when creating a token, then update those fields later to meet changing business or compliance needs. Separately, node RAM consumption has dropped by at least 10-15%, and node synchronization has become faster.
Not every cited upgrade belongs to 3.3.0
Some reports have framed the release as six upgrades already live, but that reading is inaccurate. The amendment process requires more than 80% support from trusted validators for two continuous weeks before any feature takes effect. fixCleanup3_2_0 actually belongs to the earlier 3.2.0 cycle rather than 3.3.0. For XRP holders, the immediate change is technical rather than monetary: version 3.3.0 expands the network's toolkit, but none of it guarantees higher demand or price appreciation for XRP.
Sources: crypto.news, U.Today
Trading involves risk.
Risk Disclaimer
