RippleX expects to ship xrpld 3.3.0 the week of August 1, 2026. The update includes five amendments for validator consideration — two rewritten versions of proposals that were blocked from mainnet earlier this year after critical security flaws were discovered, and three new features targeting institutional use cases. No funds were ever lost from the original flaws, but the patches are significant for the XRP Ledger's security posture.
The security fixes
Two amendments in the release are replacements for Batch and Permission Delegation, both of which were blocked before reaching mainnet. The original Batch amendment had a signature-validation bug that could have let an attacker authorize transactions from a victim's account. Researcher Pranamya Keshkamat and Cantina AI's Apex identified the flaw on February 19, 2026. UNL validators were advised to vote against Batch the same evening, and an emergency release, rippled 3.1.1, marked both Batch and fixBatchInnerSigs as unsupported.
The replacement, BatchV1_1, redesigns the authorization logic. It's flagged as supported but carries a default No vote pending validator approval. The Permission Delegation flaw was different: an invalid offline-signed transaction could charge a fee before the authorization check, potentially draining XRP from an account. The fix reclassifies the error from tec to ter and reorders checks so no fee is deducted before signature verification. Its replacement, PermissionDelegationV1_1, also has a default No designation in the 3.3.0 registry.
New institutional features
Three new amendments target institutional tokenization. Confidential MPT uses elliptic-curve cryptography and zero-knowledge proofs to keep balances and transfer amounts private while remaining auditable by designated entities. Sponsored Fees and Reserves allow institutions to cover transaction fees and reserve requirements for users, removing the need for end users to hold XRP. A third unnamed amendment rounds out the set.
The update is expected between August 3 and August 9, 2026, according to a tweet from RippleX. Validators will now decide whether to activate the rewritten amendments and the new features. The default No votes on BatchV1_1 and PermissionDelegationV1_1 mean they won't go live without explicit validator support — a cautious approach after the earlier close calls.
