RippleX has announced the next XRP Ledger software release, xrpld 3.3.0. The update puts five amendments up for validator vote, and two of them, Batch and Permission Delegation, were previously pulled by the company over critical vulnerabilities. RippleX head of product Jazzi Cooper said so on Friday.
What exactly is coming in xrpld 3.3.0?
The release is expected next week. The package carries five amendments, namely Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT. Three of them, Confidential MPT, Sponsored Fees and Reserves, and Dynamic MPT, are appearing on the network for the first time. Batch and Permission Delegation already went through voting before, but both failed after researchers found vulnerabilities.
How does the network decide which amendments to ship?
XRP Ledger amendments are not activated by Ripple the company, they are activated by the network's own validators. A proposal only takes effect once a set share of participants back it for a set stretch of time in a row. The mechanism is designed to hand the decision to the network rather than to the code's authors.
- An 80% threshold: an amendment activates only once at least 80% of trusted validators support it.
- That support has to hold for two consecutive weeks, not just once.
- If support drops below the threshold, the amendment simply does not activate.
- Ripple proposes the code but cannot force a change through without the network's votes.
Why were Batch and Permission Delegation pulled from voting?
The Batch amendment lets up to eight transactions across different accounts execute as one bundle, on an all-or-nothing basis. It reached the voting phase back in February, but researcher Pranamya Keshkamat and the firm Cantina found a flaw in how it validated signatures. The flaw would have let an attacker execute transactions from someone else's account without holding its keys. Validators were advised to reject the amendment, and an emergency release marked it unsupported before it could ever activate on the main network. No user funds were affected.
Permission Delegation lets an institution grant another account narrowly scoped authority without handing over full signing power. A vulnerability in this amendment surfaced back in September 2025, and the feature was disabled right away. The bug let one account charge fees to another account and potentially drain its balance. Since then, the XRP Ledger's documentation has listed both amendments as obsolete, and it is the revised versions that are now returning for a vote.
What do the new features add?
Confidential MPT combines zero-knowledge proofs with elliptic-curve encryption, so balances and transfer amounts on Multi-Purpose Tokens stay hidden from outsiders while auditors or regulators can still verify them when required. Sponsored Fees and Reserves lets a bank or platform cover an account's XRP fees and reserve requirement, so a user no longer has to acquire XRP first just to start a transaction. Dynamic MPT lets an issuer decide up front which token properties can be changed later, avoiding a full migration to a new token whenever fees or metadata need an update.
What this means for the network and businesses
Just two weeks ago, all five amendments were still in development, and validators were instead voting on separate bug-fix bundles for the lending protocol, single-asset vaults, and the permissioned exchange. None of these approvals is guaranteed: the lending protocol and single-asset vault proposals have each drawn roughly a third of the support they need, and Batch already has a track record of being voted down. For banks and platforms working with XRP, the most visible practical change is the ability to cover fees for customers and offer private token settlement without migrating their infrastructure.
Comments
Your email address will not be published. Required fields are marked *