XRP Ledger Brings Back Bugged Features Fixed for Institutions

RippleX Head of Product Jazzi Cooper announced that xrpld 3.3.0, expected next week, will carry five amendments including rebuilt versions of two features validators once blocked after critical bugs. The package targets privacy, atomic multi-account settlement, and fee sponsorship so institutions can treat the public XRP Ledger as usable infrastructure for tokenized assets.

Amendments still need 80 percent of the Unique Node List for two full weeks before they activate. Software ships first. Network consent comes later.

Five Amendments Ride With the Next Server Build

Cooper posted the list on 31 July. The five are Confidential MPT, Batch (as BatchV1_1), Permission Delegation (as PermissionDelegationV1_1), Sponsored Fees and Reserves, and Dynamic MPT. She framed them as the next step after the ledger already proved it can hold tokenized assets at scale.

Her exact line: “Now it’s time to put these assets to use: global transfers, trading, collateralizing, and settling.” The post listed the five amendments that move XRPL closer to those workflows.

The recent fixCleanup3_2_0 amendment already activated on 29 July after more than 85 percent validator support. That cleanup hardened vaults, lending, the permissioned DEX and multi-purpose tokens. Version 3.3.0 now adds the feature set.

The known amendments tracker and statuses already lists BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1 and Sponsor as the current names.

Why Two Features Had to Be Yanked First

Batch and Permission Delegation are not first attempts. Both reached voting phases, then hit critical flaws that forced emergency “unsupported” marks and “No” votes from the UNL.

1. 15 September 2025, Community member tequ reported the Permission Delegation fee-drain bug on devnet. An account could force transaction fees onto another account under certain offline-signed conditions, even without proper permissions.
2. 29 September 2025, Official disclosure published. The original amendment was disabled in 2.6.1 and later; a V1_1 replacement was planned.
3. 19 February 2026, Researcher Pranamya Keshkamat and Cantina’s Apex tool found a signature-validation loop error in Batch. An attacker could craft a batch that executed payments from arbitrary victim accounts without their keys.
4. 23 February 2026, Emergency rippled 3.1.1 marked Batch and fixBatchInnerSigs unsupported. No mainnet activation, no funds lost.
5. Late July 2026, Cooper confirms the corrected BatchV1_1 and PermissionDelegationV1_1 ship inside 3.3.0 for a fresh validator vote.

The Batch signature-validation flaw report details the early-exit bug: the check succeeded on a newly created account and skipped remaining signers. The Permission Delegation fee-drain disclosure shows the tec-error ordering that charged fees before signature validation.

In both cases the amendment process itself stopped the damage. Validators vetoed. Software made the features unsupported. No mainnet funds moved. That sequence is the pattern now repeating in reverse: fixed code returns for a second vote.

What the Rebuilt Features Do

BatchV1_1 lets a single outer transaction carry up to eight inner transactions across different accounts. All succeed or none do. That enables delivery-versus-payment and atomic settlement without trusting an intermediary to reverse one side if the other fails.

Permission Delegation V1_1 gives an institution the on-chain equivalent of role-based access. Treasury keeps the issuance keys. Trading desks or ops teams receive only the specific transaction types and limits they need. Full signing authority never leaves the secure enclave.

• Batch removes the need for multi-step, trust-heavy coordination across counterparties.
• Permission Delegation satisfies the separation-of-duties rules most banks already run internally.
• Both now carry the extra guards that the earlier versions lacked.

The original Batch amendment even had a companion fixBatchInnerSigs that itself became unsupported. The V1_1 package folds the corrected logic into one clean proposal.

Privacy and Sponsorship Close the Remaining Gaps

Confidential MPT is the feature many institutions have waited for. It keeps balances and transfer amounts private on the public ledger by combining zero-knowledge proofs with elliptic-curve encryption. Designated auditors or regulators can still open the numbers when required. The Confidential Transfers XLS-96 specification calls this institutional-grade privacy with compliance hooks intact.

For financial institutions, privacy is often a prerequisite for using public blockchain infrastructure.

Cooper wrote that line herself. Without it, many banks simply stay on permissioned chains or private ledgers.

Sponsored Fees and Reserves attacks the other classic barrier. A bank, issuer or platform can pay the XRP transaction fees and the account reserve for end users. The users still own their keys and accounts. They no longer need to acquire and manage XRP just to open an account or send a first transfer. Onboarding friction drops.

Dynamic MPT rounds out the set. At issuance the creator marks which properties (transfer fees, metadata, selected flags) may be updated later. No more full token migration and holder migration when rules or compliance needs change.

How the Package Fits Recent Network Moves

Two weeks ago the live voting set still centered on bug-fix bundles for lending, single-asset vaults, the permissioned DEX and multi-purpose tokens. Those rails are now firmer after fixCleanup3_2_0. The five new amendments sit on top of that base.

Lending Protocol and Single Asset Vault amendments have hovered around one-third support so far, well short of the 80 percent bar. Batch already carries the memory of a prior failed vote. Nothing in 3.3.0 is guaranteed to activate just because the software ships.

Crowd reaction on X has focused less on price and more on the security loop. One recurring observation is that the same veto process that killed the broken versions now gets a chance to approve the hardened ones. Privacy replies repeatedly call Confidential MPT the missing institutional piece. Sponsored fees draw quieter but consistent nods from people who have watched retail and corporate onboarding stall on the XRP acquisition step.

Validator Approval Remains the Real Gate

Cooper was explicit: the release is anticipated next week. Amendments activate only after validator approval. Operators are urged to review the specs as they appear. Ripple plans technical deep dives, implementation guides and security reviews in the following weeks.

The 80 percent threshold for two consecutive weeks is deliberate. It keeps any single entity, including Ripple, from forcing protocol changes. That same rule is why the earlier bugs never reached mainnet balances. It is also why the fixed versions must re-earn the supermajority from scratch.

If the five clear the bar, institutions gain native private token balances, atomic multi-party settlement, scoped delegation, fee sponsorship and mutable token parameters on the same public ledger that already settles in seconds. If they stall, the software still runs and the cleanup work from 3.2.0 remains. The network simply waits for the next round of votes.

The historical pattern is visible in plain sight. Features that once carried keyless-drain and fee-drain risks were stopped cold. The corrected code now asks the same validators for a second chance, this time alongside the privacy and sponsorship tools that turn tokenized assets into something banks can actually use.