XRP Ledger’s xrpld 3.3.0 Revives Two Bug-Pulled Features, Needs 80% Validator Vote

The XRP Ledger’s validators are being asked to approve five protocol amendments in the upcoming xrpld 3.3.0 release, two of which were previously withdrawn from the network after researchers found bugs that could have enabled unauthorized transactions or fee draining. Jazzi Cooper, head of product at RippleX, said on July 31 that the release is expected next week, and each change still needs backing from at least 80% of trusted validators for two consecutive weeks before it can activate.

That 80%-for-14-days threshold is XRPL’s built-in safeguard: it puts the decision on what code actually ships in the hands of the validator set rather than Ripple alone. For holders and builders, the number matters because it sets a hard floor on how fast — or slow — new functionality can reach the live network, and it means any of these five proposals can still be rejected if validator support falls short.

Two features return after security setbacks

Batch and Permission Delegation are both making a second run at the amendment process after failing to clear it previously. Batch is designed to let up to eight transactions across different accounts execute atomically — either all of them succeed or none do — which is aimed at cross-account settlement use cases. Permission Delegation would let institutions grant narrowly scoped signing authority to a third party without handing over full account control.

Both were pulled from the network earlier after security researchers flagged bugs serious enough to warrant emergency action, with the flaws described as capable of enabling unauthorized transactions or draining transaction fees. The versions now up for validator approval in xrpld 3.3.0 have been revised to address those issues.

Three new amendments target institutional and tokenized-asset use

The release also introduces three amendments that have not previously been proposed to validators. Confidential MPT is built to support private activity around tokenized assets. Sponsored Fees and Reserves would let institutions cover XRP transaction costs on behalf of their users. Dynamic MPT is intended to make certain token properties adjustable without requiring a full asset migration.

Cooper framed the release as a shift from proving XRPL can host tokenized assets to putting them to work. “XRPL has already proven it can support tokenized assets at scale. Now it’s time to put these assets to use: global transfers, trading, collateralizing, and settling,” she wrote on X.

Why the validator vote matters more than the code

None of these five amendments changes anything for XRP holders or dApps unless validators actually vote them in. The 80%-over-two-weeks bar has repeatedly slowed or blocked amendments on XRPL, and it is precisely why Batch and Permission Delegation were able to be pulled back once bugs surfaced rather than shipping to a live, adversarial network.

For institutions eyeing XRPL for tokenized-asset settlement, the practical signal is in the mix of features rather than any single one: sponsored fees and confidential MPT point toward enterprise-grade, privacy-aware asset issuance, while batch execution and delegated permissions point toward more complex multi-party transaction flows. Whether any of that reaches production now depends on how the validator set votes over the coming weeks.

Sources

• coindesk.com
• coingape.com