The XRP Ledger will put five protocol changes in front of its validators next week, and two of them were taken offline in the past year after security researchers found bugs serious enough to trigger emergency releases. Jazzi Cooper, head of product at RippleX, said on Friday that the xrpld 3.3.0 release carries Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT. Batch and Permission Delegation have both been through the voting process before and failed it. XRP traded at $1.06 on Saturday morning, close to flat over 24 hours, with a market value near $66 billion.
An amendment is a proposed change to the XRP Ledger’s rules that activates only after at least 80% of trusted validators back it for two consecutive weeks. Validators are the independent servers that run the network and agree on its transaction history, and the threshold is set so the network rather than Ripple decides what ships.
Key takeaways
- The xrpld 3.3.0 release is expected next week with five amendments, according to RippleX head of product Jazzi Cooper.
- Batch and Permission Delegation return after both were disabled over flaws that allowed unauthorized transactions and fee draining.
- Three new amendments cover private tokenized assets, sponsored network fees, and token properties that can be changed after issuance.
- Each needs 80% validator support for two straight weeks. Two amendments already on the ballot sit near one third.
Published: August 1, 2026, 16:30 UTC
Two features return after emergency shutdowns
Batch and Permission Delegation are the only amendments in this release with a documented history of being pulled for security reasons.
Batch, formally XLS-56, lets up to eight transactions across different accounts execute together so that either all of them succeed or none do. It reached its voting phase in February. Security researcher Pranamya Keshkamat and the firm Cantina then found a loop error in the function that validated batch signatures, which would have let an attacker execute transactions from any account without holding its keys.
Validators were advised to vote no, and an emergency server release marked both Batch and the related fixBatchInnerSigs as unsupported to block activation. No funds were lost because the amendment never reached the main network.
Permission Delegation lets an institution grant another account narrowly scoped signing authority without handing over full control of an account. It was disclosed as vulnerable in September 2025 and disabled after researchers found that one account could charge transaction fees to another and potentially drain its balance. The ledger’s documentation has listed both amendments as obsolete since, pending revised versions.
What the three new amendments do
The remaining three amendments have never been voted on and target institutional use of tokenized assets.
Confidential MPT pairs zero-knowledge proofs with elliptic-curve encryption so that balances and transfer amounts on Multi-Purpose Tokens stay private while auditors or regulators can still verify them on request. A zero-knowledge proof is a method of proving a statement is true without revealing the data behind it.
Sponsored Fees and Reserves lets a bank or platform cover another account’s XRP transaction fees and reserve requirement. That removes the step where every end user has to acquire XRP before they can transact, a friction point for any firm onboarding customers who have never held a token.
Dynamic MPT lets an issuer decide at creation which properties of a token can be changed later, so updating fees or metadata does not force a full migration to a new token.
Why the release matters for institutions
The package reads as an attempt to make tokenized assets usable rather than merely issuable.
Privacy with selective disclosure addresses a recurring compliance objection to public blockchains, where a corporate treasury cannot expose counterparty balances to competitors. Scoped delegation maps to how approval hierarchies already work inside banks, where a junior operator can move funds within limits without holding master keys. Sponsored fees remove the requirement that a customer buy a volatile asset just to send a stablecoin.
Ripple has been building toward institutional rails on several fronts, including opening RLUSD minting to institutions and securing a full MiCA license across 30 EEA countries. The amendments in 3.3.0 sit on the protocol side of that same push, alongside wider regulatory work on tokenized finance.
Approval is not guaranteed
Shipping the code is not the same as activating it, and the current ballot suggests validators are in no hurry.
The lending protocol and single-asset vault amendments have each drawn roughly a third of validator support against the 80% they need, according to CoinDesk. Two weeks ago all five of the new amendments still sat in development on the XRP Ledger amendment tracker, with validators voting instead on bug-fix bundles for the lending protocol, single-asset vaults, the permissioned exchange, and multi-purpose tokens.
Batch also carries the memory of February. Validators who were told to reject it once may want more review time before backing a revised version, which means the earliest realistic activation for anything in 3.3.0 is two weeks after the 80% threshold is first crossed.
Frequently asked questions
What is xrpld 3.3.0?
It is the next software release for the XRP Ledger, expected the week of August 3, 2026. It contains five proposed amendments. Installing the release does not activate the features. Validators must vote them in separately under the ledger’s 80% approval rule.
Why were Batch and Permission Delegation disabled?
Researchers found flaws in both. Batch had a signature-validation error that could have let an attacker send transactions from accounts they did not control. Permission Delegation allowed one account to charge fees to another and potentially drain it. Neither flaw reached the main network.
When could these features go live on the XRP Ledger?
Only after at least 80% of trusted validators support an amendment for two consecutive weeks. Two amendments currently on the ballot sit near one third of that threshold, so activation for the 3.3.0 features is not expected immediately after release.
