XRP Ledger is shipping version 3.3.0 next week with five amendments, including restored versions of Batch and Permission Delegation features that were previously pulled after researchers discovered critical vulnerabilities.
Batch and Permission Delegation were withdrawn before reaching mainnet after security researchers found bugs that could have allowed attackers to move funds from accounts they did not control. No funds were lost because the flawed code never ran on the live network. Both features are returning with fixes in the new release, according to a post from Jazzi Cooper, a core contributor to XRP Ledger development.
The five amendments in version 3.3.0 are Confidential MPT, BatchV1_1, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT. Sponsored Fees addresses a long-standing friction point for institutional adoption: the feature allows banks and other entities to pay XRP transaction costs on behalf of users, removing the requirement that end users acquire XRP to interact with the ledger. This capability requires validator approval to activate on the live network.
Batch functionality consolidates multiple transactions into a single ledger operation, reducing processing overhead and costs for applications that submit high volumes of related operations. Permission Delegation allows account holders to grant limited transaction rights to other parties without sharing full control of their keys, a mechanism useful for custodians and institutional account management.
The XRP Ledger is an open-source blockchain maintained by a decentralized network of validators. Major financial institutions including Ripple, the company that originally created the ledger, run validator nodes. The network processes payments and settlements, with proponents targeting use cases in cross-border remittance and institutional fund movement.
The return of Batch and Permission Delegation marks the second cycle for both amendments. The ledger's governance model requires supermajority validator support to activate amendments, meaning new code must pass both technical review and network-wide approval before reaching mainnet. Both features were submitted, flagged as unsafe during security audits, and rejected before activation. The fixes now in testing address the specific attack vectors identified in the earlier reviews.
Version upgrades to the XRP Ledger typically roll out over weeks as validators choose when to update their software, meaning the features will not activate immediately even after 3.3.0 ships. Validators must adopt the release and then vote to activate each amendment separately.
