XRPL v3.3.0 Revives Two Security-Patched Amendments

Batch permits up to eight transactions across different accounts to execute together in an all-or-nothing fashion within a single ledger close. That atomic approach enables complex workflows like delivery-versus-payment without external trust assumptions. The feature had reached validator voting in February 2026 before security researcher Pranamya Keshkamat, working with Cantina, uncovered a critical weakness in its signature-validation logic. An attacker could have executed transactions from arbitrary accounts without holding the corresponding keys, Keshkamat said. Validators were advised to reject the proposal, and an emergency software release marked the amendment unsupported to prevent activation. Because it never reached the main network, no balances were affected. A corrected implementation is now part of v3.3.0.

Permission Delegation lets an institution assign narrowly defined transaction rights to another account while retaining full control of signing authority. That supports role-based access common in institutional settings. A vulnerability disclosed in September 2025 showed the original design could allow one account to impose fees on another and potentially drain its balance. The feature was disabled, and both original proposals were later listed as obsolete pending revised versions.

Confidential MPT pairs zero-knowledge proofs with elliptic-curve encryption so that Multi-Purpose Token balances and transfer amounts remain private on the public ledger. Authorized parties such as auditors or regulators can still verify details when required. Sponsored Fees and Reserves enables a bank, issuer, or platform to cover another account’s XRP transaction costs and reserve requirements, letting account holders keep ownership of their keys while avoiding the need to obtain XRP just to interact with the network. Dynamic MPT allows an issuer to specify at creation time which token properties may later be adjusted, avoiding a full migration to a new token when transfer fees, metadata, or other settings must change in response to business or regulatory developments.

None of the amendments activate automatically. On the XRP Ledger, protocol changes take effect only after at least 80 percent of trusted validators sustain support for two consecutive weeks. The process keeps decision-making with the broader network.

The upcoming release restores previously paused capabilities in strengthened form while adding tools focused on privacy, easier institutional onboarding, and greater operational flexibility. Validators will determine the timeline through their voting.