The XRP Ledger's next major software release will ask validators to vote on five protocol amendments, including two that were previously pulled after security researchers discovered flaws capable of allowing unauthorized transactions and fee draining.
Jazzi Cooper, head of product at RippleX, announced Friday that xrpld 3.3.0 is expected to ship next week, carrying amendments that significantly expand the ledger's capabilities for institutional tokenization and cross-account transaction coordination.
Returning From the Dead
Two of the five amendments have been through the validator voting process before — and failed.
The Batch amendment allows up to eight transactions across different accounts to execute atomically: either all succeed or none do. It reached the voting phase in February but was rejected after security researcher Pranamya Keshkamat and the audit firm Cantina identified a vulnerability in how the amendment validated signatures. The flaw would have allowed an attacker to execute transactions from any account without holding its keys.
Validators were advised to reject the amendment, and an emergency server release marked it unsupported to prevent activation. No funds were lost because the flaw was caught before the amendment could reach mainnet.
Permission Delegation, which lets institutions grant another account narrowly scoped signing authority without handing over full control, suffered a similar fate in September 2025. Its bug allowed one account to charge transaction fees to another and potentially drain its balance.
Both amendments return in xrpld 3.3.0 with revised implementations.
Three New Additions
The remaining three amendments are new:
Confidential MPT combines zero-knowledge proofs with elliptic-curve encryption to keep balances and transfer amounts on Multi-Purpose Tokens private. Regulators or auditors retain the ability to verify transactions when required, a design aimed squarely at institutional adopters who need confidentiality without sacrificing compliance.
Sponsored Fees and Reserves allows a bank or platform to cover another account's XRP transaction fees and minimum reserve requirements. This removes one of the most persistent friction points for institutional adoption: the requirement that every end user acquire and hold XRP before transacting.
Dynamic MPT lets token issuers specify at creation which properties of a Multi-Purpose Token can be modified later. This avoids the need for a full token migration when parameters such as fees or metadata require updating — a practical concern for institutions managing large-scale tokenized asset programs.
The Validator Gate
None of these features will activate automatically. XRP Ledger amendments require at least 80% of trusted validators to approve them for two consecutive weeks before they take effect. This threshold is designed to ensure that the network — rather than Ripple — decides what ships.
That gate is not trivial. The lending protocol and single-asset vault amendments currently sit at roughly one-third of validator support, well below the threshold. Batch already has a track record of being voted down.
The amendment process reflects a broader tension in XRP Ledger development: features designed for institutional use cases must win support from a validator set that includes entities with diverse and sometimes conflicting priorities.
Tokenization as Strategy
The release underscores RippleX's strategic focus on real-world asset tokenization — a category that has attracted significant attention from financial institutions and blockchain platforms alike.
Confidential MPT in particular addresses a genuine institutional requirement. Banks and asset managers operating under regulatory regimes in the EU, U.S., and Asia need the ability to conduct private transactions on public infrastructure while still demonstrating compliance to regulators on demand. The combination of zero-knowledge proofs with designated auditor access is an architectural pattern that has gained traction across multiple blockchain platforms in 2026.
Whether validators agree that these features are ready — this time — will be determined in the coming weeks.