The XRP Ledger is restoring two core features withdrawn in 2025 after critical security vulnerabilities were discovered in each. Version 3.3.0, scheduled to arrive between August 3 and 9, will reintroduce Batch and Permission Delegation with fixes applied to the signature validation flaw that plagued Batch and the fee-draining vulnerability that disabled Permission Delegation.
Batch processing allows multiple transactions to be submitted and confirmed as a single atomic unit. Permission Delegation enables an account holder to grant another address authority to execute specific transaction types on its behalf without holding the account's master key. Both features had been core to the ledger's transaction model before their removal over a year ago.
The Batch flaw centered on improper signature validation that could have allowed an attacker to forge or replay transaction signatures within a batch, potentially authorizing unintended transfers or state changes. Permission Delegation's vulnerability was rooted in a fee calculation error that permitted a delegated account to drain reserves from the authorizing account through repeated low-cost operations.
Ripple and the XRP Ledger Foundation removed both features in 2025 rather than ship patches alongside the live network. The decision halted workflows that depended on atomic transaction settlement and key delegation patterns common in institutional custody and payment processing applications.
Version 3.3.0 also introduces three additional amendments beyond the restored features, according to documentation. The upgrade requires consensus from the network's validators to activate; validators represent independent operators running ledger nodes across exchanges, custodians, and market makers.
The restoration marks the first time the ledger has reactivated a major feature class after removal for security reasons. Prior protocol upgrades have added new functionality or deprecated features deemed obsolete, but few have required re-vetting and re-implementation of previously live code at the same scope.
