Community Trust ScoreVerified
The XRP Ledger is getting a significant software push. Version xrpld 3.3.0 is due out next week, carrying five amendments — two of which were yanked from the network after researchers caught serious security holes.
Jazzi Cooper, head of product at RippleX, put out word on the upcoming release. The five amendments are Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT. Together they’re meant to sharpen the ledger’s capacity for global transfers, trading, and settlement. That’s a pretty wide scope for a single release, and it’s worth understanding what each piece actually does — and why two of them are coming back from the dead.
Batch nearly made it out the door before. Designed to let users fire off up to eight transactions at once, it got pulled after security researcher Pranamya Keshkamat and the firm Cantina spotted a flaw in the signature validation process. That flaw could have let unauthorized transactions slip through. Validators rejected it. Now a revised version is back in the queue.
Why Permission Delegation Got Pulled in September 2025
Permission Delegation had a rougher exit. It went down in September 2025 after developers found potential vulnerabilities that could drain accounts. The feature is built to let one party delegate limited authority to another without handing over full signing power — useful for institutional setups where you want some separation of duties. But the original version was too risky to leave live, so it got disabled fast. The revised build is now part of the 3.3.0 package.
Both cases are a reminder of how unforgiving blockchain security can be. A flaw that might be a minor bug in a traditional app can become a funds-at-risk emergency on a live ledger. The network moved quickly both times, which is probably the right call, even if it delayed the features.
What the Three New Amendments Actually Do
The three genuinely new additions are worth unpacking. Confidential MPT uses zero-knowledge proofs and elliptic-curve encryption to keep transaction details private while still letting auditors verify what happened. It’s a balancing act — privacy for users, transparency for compliance. That combination matters a lot for institutional players who can’t just broadcast every transaction to the world.
Sponsored Fees and Reserves is maybe the most user-friendly of the bunch. It lets a third party — say, a bank or a fintech platform — cover another account’s XRP fees. Right now, anyone who wants to transact on the ledger needs to hold some XRP first. That’s a friction point, especially for onboarding new users who aren’t already in the crypto ecosystem. Sponsored Fees removes that barrier. You can transact without needing XRP in your pocket upfront.
Dynamic MPT rounds out the set. It lets issuers tweak token properties without spinning up entirely new tokens. If something about a tokenized asset needs to change — interest rate, metadata, whatever — the issuer can adjust it in place. No messy migrations. That kind of flexibility is increasingly important as more real-world assets get tokenized and need to evolve over time.
The 80% Validator Threshold Is No Guarantee
Getting these amendments live isn’t automatic. The XRP Ledger runs on a governance model where amendments need at least 80% approval from trusted validators for two consecutive weeks before they activate. Ripple can’t just flip a switch. The validator community decides.
And they’ve said no before. Batch’s first run is proof of that. Right now, other pending amendments — the lending protocol and single-asset vaults — are still short of the 80% mark. So even well-designed features can sit in limbo.
It’s unclear exactly when validator voting on the 3.3.0 amendments will formally begin. No specific timeline beyond “next week” for the release was given. The approval window after that could stretch.
What’s clear is that the ledger’s amendment tracker has expanded. Previously, validators were only voting on bug-fix bundles tied to the lending protocol, single-asset vaults, permissioned exchange, and multi-purpose tokens. The 3.3.0 batch is a broader, more ambitious set of changes.
Cooper’s announcement didn’t specify whether all five amendments will be bundled for a single vote or handled separately. That distinction matters — a bundled vote means validators accept or reject the whole package, while separate votes give them more granular control. No details on that yet.
The revised Batch and Permission Delegation features went through what Cooper’s team apparently treated as a full security overhaul before resubmission. Whether validators agree the fixes are sufficient is the next question. Their track record on Batch alone says they won’t rubber-stamp it.
Hub: XRP price, news, and analysis
Frequently Asked Questions
What are the five amendments in XRP Ledger’s xrpld 3.3.0 update?
The five amendments are Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT, all aimed at improving transaction flexibility, privacy, and settlement on the XRP Ledger.
Why were Batch and Permission Delegation removed from the XRP Ledger before?
Batch was pulled after researcher Pranamya Keshkamat and Cantina found a signature validation flaw that could allow unauthorized transactions; Permission Delegation was disabled in September 2025 after vulnerabilities were found that could drain accounts.
