XRP Ledger 3.3.0 brings privacy and batch upgrades

XRP Ledger developers released xrpld version 3.3.0 on Aug. 6, moving several protocol changes closer to possible mainnet activation. Summary XRPL 3.3.0 introduces protocol code, but validator approval remains necessary before any mainnet activation occurs. ConfidentialTransfer would shield MPT balances and transfer amounts while preserving compliance access for authorized parties. BatchV1_1 restores atomic transaction functionality after an earlier version was halted over a security flaw. Sponsor would let third parties cover fees and reserves while users retain full account control. DynamicMPT would let issuers modify selected token properties later, supporting evolving business and compliance needs. The official GitHub release confirms work on ConfidentialTransfer, BatchV1_1, Sponsor and DynamicMPT, alongside fixes and other protocol changes. The software release itself does not activate those features on the network. The distinction matters because some reports describe six upgrades as already live. Under the XRP Ledger amendment process, new protocol features require validator support before activation. An amendment must maintain more than 80% support from trusted validators for two continuous weeks before taking effect. XRP Ledger 3.3.0 upgrades You might also like: XRP Ledger adds Ankr nodes ahead of v3.3.0 XRP Ledger 3.3.0 adds privacy and atomic transaction tools ConfidentialTransfer is designed to add privacy for Multi-Purpose Tokens, or MPTs. XRPL documentation says 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. The feature remains subject to amendment activation, so private MPT transfers should not yet be described as active on XRPL mainnet. BatchV1_1 is another major component. The XLS-56 standard allows multiple transactions to be packaged and processed together, including transactions involving different accounts. Atomic execution can help settlement workflows where several actions must succeed together rather than leaving one leg completed while another fails. Revised features follow earlier security findings Batch has an important history. An earlier version was disabled before mainnet activation after a security issue was discovered in transaction-signing logic. The XRPL Foundation later moved toward BatchV1_1 as the corrected replacement. As previously reported in XRPL security coverage, developers have increased formal review around recent upgrades. Permission Delegation followed a similar path. XRPL disclosed in September 2025 that a bug in the earlier amendment could have allowed an unauthorized transaction to charge fees to another account under specific conditions. Validators were advised to vote no, and the vulnerable feature never activated. PermissionDelegationV1_1 was developed as its replacement. The revised concept lets an account grant defined transaction permissions without handing over its main private key, supporting operational wallets with limited authority. Sponsor and DynamicMPT target institutional onboarding Sponsor, based on XLS-68, is designed to let another account cover transaction fees or reserve requirements while the user keeps control of the account and keys.