TechXRP Ledger's Upcoming Upgrade Revives Previously Withdrawn Features

The anticipated xrpld 3.3.0 release is set for next week, featuring five proposed amendments, including two revised functionalities that were previously removed due to critical bugs.

By Shaurya Malwa Aug 1, 2026, 6:09 a.m. 2 min readMake preferred on ShareShare this articleCopy linkX (Twitter)LinkedInFacebookEmailMake preferred on XRP Ledger's Upcoming Upgrade Revives Previously Withdrawn Features. (Kevin Ku/Unsplash/Modified by CoinDesk)SummaryShow
  • The upcoming xrpld 3.3.0 release of the XRP Ledger will present validators with five proposed amendments, including revised versions of the previously flawed Batch and Permission Delegation features.
  • The Batch feature enables up to eight cross-account transactions to be executed atomically, while Permission Delegation allows institutions to grant limited signing authority without full control.
  • New amendments—Confidential MPT, Sponsored Fees and Reserves, and Dynamic MPT—aim to facilitate private tokenized asset activities, enable institutions to cover users' XRP costs, and allow certain token properties to be altered without complete migrations, all requiring 80% validator approval for two weeks.

The XRP Ledger is preparing for its next software update, which will propose five new features to validators, two of which were previously removed due to significant security vulnerabilities identified by researchers.

Jazzi Cooper, the head of product at RippleX, announced on Friday that the xrpld 3.3.0 release is expected to include Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT.

XRPL has already demonstrated its capability to support tokenized assets at scale. Now it’s time to leverage these assets for global transfers, trading, collateralization, and settlement.

The upcoming xrpld 3.3.0 release includes five amendments that significantly advance XRPL towards that objective.…

— Jazzi Cooper (@jazzicoop) July 31, 2026

For an amendment to take effect, it must receive at least 80% approval from trusted validators over two consecutive weeks, ensuring that the network, rather than Ripple, determines the changes implemented.

Both the Batch and Permission Delegation amendments have undergone this approval process previously but did not succeed.

The Batch feature, which allows for up to eight transactions across various accounts to execute simultaneously, was put to a vote in February.

Security researcher Pranamya Keshkamat and the firm Cantina identified a vulnerability in the amendment's signature validation process that could have enabled an attacker to initiate transactions from any account without possessing the necessary keys.

Validators were advised to reject the feature, leading to an emergency server update that rendered it unsupported to prevent its activation. Fortunately, no funds were lost, as it never reached the main network.

Permission Delegation, which permits an institution to assign limited authority to another account without transferring complete signing power, was found to have vulnerabilities in September 2025 and was subsequently disabled.

This bug permitted one account to impose transaction fees on another, potentially draining its balance. Both amendments have since been marked as obsolete in the ledger's documentation, awaiting replacement with improved versions.

(Shaurya Malwa/CoinDesk)

The remaining three amendments are new introductions. Confidential MPT integrates zero-knowledge proofs, allowing verification of a statement's truth without disclosing the underlying data, alongside elliptic-curve encryption. This ensures that balances and transfer amounts on Multi-Purpose Tokens remain confidential while allowing audits or regulatory checks when necessary.

Sponsored Fees and Reserves enable a bank or platform to cover another account's XRP fees and reserve requirements, eliminating the necessity for every user to acquire XRP prior to engaging in transactions.

Lastly, Dynamic MPT allows issuers to specify which token properties can be modified at creation, thereby avoiding a comprehensive migration to a new token when updates to fees or metadata are required.

This release signifies a notable shift from the ledger's status just two weeks ago. In mid-July, all five amendments were still in development, and the validators could only vote on a collection of bug-fix bundles related to the lending protocol, single-asset vaults, the permissioned exchange, and multi-purpose tokens.

Approval is not guaranteed. The amendments concerning the lending protocol and single-asset vault have only garnered about one-third of the necessary validator support, far short of the required 80%; Batch already has a history of being voted down.