The XRP Ledger has released xrpld version 3.3.0, putting a package of six proposed amendments before validators as the network considers a broad expansion of its privacy, transaction, token-management, and institutional capabilities.
The proposals include Confidential Transfer, Batch, Permission Delegation, Sponsor, Dynamic MPT, and a bundled cleanup amendment. None of these features should be considered active on the XRP Ledger yet. Under the network’s amendment process, a proposal must maintain more than 80% validator support for two consecutive weeks before it can activate.
The release follows several months of development work around the next generation of XRP Ledger functionality. Development activity shows support being added across the XRPL software ecosystem for features including Batch V1.1, Dynamic MPT, and the new cleanup amendment ahead of the 3.3.0 release.
XRPL validator Vet described the package as a major release, highlighting privacy, transaction batching, sponsored fees, delegated permissions, and token flexibility among the changes heading into the voting process.
Privacy and transaction upgrades lead the proposal
Confidential Transfer is the most notable privacy-focused proposal in the XRP Ledger v3.3.0 package. According to the official XRPL amendment documentation, the feature is designed to provide institutional-grade privacy for Multi-Purpose Tokens (MPTs) using EC-ElGamal encryption and zero-knowledge proofs.
XRP Ledger v3.3.0 has launched with six proposed amendments now open for validator voting. Source: XRP Ledger Operations via X
The proposed system would shield individual MPT balances and transfer amounts from public view while retaining mechanisms that allow authorized parties, such as issuers or auditors, to verify relevant information. This distinction is important for institutional use cases, where transaction confidentiality may need to coexist with reporting and regulatory requirements.
The Batch amendment addresses a different limitation by allowing multiple transactions to be executed as a single atomic operation. The updated Batch V1.1 implementation has also been incorporated into XRPL developer tooling, including xrpl4j, as work progressed toward the 3.3.0 release.
Atomic execution means the transactions in a batch are treated as one coordinated operation rather than a series of independent actions. That can be useful for more complex settlement flows, including transactions that need several steps to succeed together.
Permission Delegation is aimed at account management and institutional security. The feature allows an account owner to assign specific transaction permissions to another account without handing over control of the primary account’s keys.
The approach can separate operational duties from asset custody. For example, an organization could maintain assets in a more secure account while allowing another wallet to perform narrowly defined transactions. The proposal is also a revised version of an earlier Permission Delegation implementation. XRPL developers previously disabled that version after a vulnerability was identified, with PermissionDelegationV1_1 developed as its replacement.
Sponsor introduces another change that could affect how applications interact with the XRP Ledger. It allows one account to cover transaction fees and reserve requirements for another account under defined conditions.
For developers, sponsored costs could make applications easier to use because newcomers would not necessarily need to manage XRP for every initial network interaction. The underlying goal is to reduce friction around account funding and transaction execution.
@Vet_X0, an XRP Ledger validator, calls XRPL v3.3.0 a major release featuring the network’s first native privacy amendment for encrypted MPT balances and transfers. Source: @Vet_X0 via X
Dynamic MPT, meanwhile, focuses on token issuers. The amendment is associated with XLS-94 and is designed to make selected properties of Multi-Purpose Tokens changeable after issuance. That gives issuers additional flexibility when managing tokenized assets whose operational requirements can evolve over time. XRPL documentation currently lists DynamicMPT as an amendment in development.
The sixth proposal, FixCleanup, groups technical fixes intended to improve protocol stability and address issues within the XRP Ledger’s implementation.
Together, the amendments cover several different layers of the network. Confidential Transfer focuses on privacy, Batch on transaction composition, Permission Delegation on account control, Sponsor on user experience, and Dynamic MPT on token management.
Performance improvements now await validator approval
The 3.3.0 release also includes infrastructure work intended to improve the experience of running XRP Ledger nodes. Development updates have highlighted efforts to reduce resource requirements and improve synchronization for node operators.
XRPL v3.3.0 introduces Confidential Transfers, using EC-ElGamal encryption and zero-knowledge proofs to shield MPT balances and transfer amounts while preserving cryptographic verifiability. Source: @iamalijandro via X
Earlier reports based on Vet’s development updates cited potential memory reductions ranging from roughly 10% to as much as 40% in certain conditions. The more conservative figures associated with the current release indicate memory usage reductions of around 10% to 15%. The exact benefit can vary depending on the node’s workload and environment.
Lower resource consumption matters because validators and other node operators must continuously maintain and synchronize ledger data. Improvements in memory efficiency and synchronization can reduce the infrastructure burden associated with operating the network.
The upgrade also reflects the iterative nature of XRP Ledger development. Several components in version 3.3.0 have undergone revisions before reaching the validator stage. Batch and Permission Delegation, in particular, have previously required changes following security reviews and subsequent development work.
The validator vote is therefore the next critical step rather than the final confirmation that the features will become part of the live protocol.
Each amendment must maintain the required supermajority for two consecutive weeks before activation. XRPL’s official documentation states that amendments that meet this threshold can become enabled on the mainnet, while proposals that fail to sustain sufficient support do not activate.
If the six proposals clear that process, the XRP Ledger would gain a broader set of native tools for confidential token transfers, atomic transactions, delegated account permissions, sponsored costs, and flexible MPT management.
For institutions exploring tokenized assets, the combination is particularly relevant because it addresses several practical requirements at once: privacy, controlled access, transaction coordination, and token administration. However, the significance of the upgrade will ultimately depend on validator approval and subsequent adoption by developers and network participants.
