Key facts
- The XRP Ledger's upcoming xrpld 3.3.0 release includes five proposed amendments.
- Revised versions of the Batch and Permission Delegation features, previously withdrawn due to critical bugs, are among the proposals.
The XRP Ledger's upcoming xrpld 3.3.0 release will present validators with five proposed amendments, including revised versions of the Batch and Permission Delegation features that were previously withdrawn due to critical bugs. Three new features are also included.

This upgrade signifies a crucial step in enhancing the XRP Ledger's capabilities for tokenized assets and institutional use cases, despite the challenges posed by previously identified security vulnerabilities.
The XRP Ledger is set to introduce its xrpld 3.3.0 software release, which will put five proposed amendments before validators. Notably, two of these amendments—Batch and Permission Delegation—are revised versions of features that were previously pulled from the network due to critical security flaws. The Batch amendment aims to allow up to eight cross-account transactions to execute atomically, meaning they all succeed or fail together. Permission Delegation is designed to let institutions grant specific, limited signing authority to other accounts without relinquishing full control.
In addition to these reintroduced features, the release includes three entirely new amendments. Confidential MPT will leverage zero-knowledge proofs and encryption to keep balances and transfer amounts private on Multi-Purpose Tokens while allowing verification when needed. Sponsored Fees and Reserves will enable entities like banks to cover users' XRP transaction fees and reserve costs, potentially lowering barriers to entry. Dynamic MPT will allow issuers to specify which token properties can be modified after creation, avoiding the need for full token migrations when updates are required.
Amendments on the XRP Ledger require a significant consensus, with at least 80% of trusted validators needing to approve them for two consecutive weeks before activation. Both the Batch and Permission Delegation amendments have previously undergone this process and failed to gain sufficient support. Security researchers had identified vulnerabilities in earlier versions, leading to advisories against their activation and emergency measures to prevent their deployment. The ledger's documentation has since listed these original amendments as obsolete, paving the way for these revised versions.