XRP Ledger (XRPL) developers have put forward four code changes under the proposed fixCleanup3_5_0 amendment to close gaps that allow restricted tokens to reach some accounts without a fresh issuer approval. The work covers trust-line carve-outs, automated market maker (AMM) pool tokens, and permission checks, and the fixes still need code merges and validator support before they can go live — a development that matters for readers who track issued assets on XRPL.

Four Approval Loopholes for Restricted Tokens

The package is tracked in open rippled pull requests under fixCleanup3_5_0, including pull request no. 8648. It targets how XRPL enforces issuer-set permissions, rules that let issuers choose which accounts can receive and hold their tokens. Issuers of stablecoins and tokenized funds that require tight control rely on these settings.

On XRPL, accounts open authorized trust lines to hold issued tokens, and issuers can require approval before those lines become active — in effect an allowlist for issued tokens. Developers found paths that could still send locked tokens to accounts that lack that approval. The four fixes add stronger checks on those paths.

One change would require an issuer approval for both assets in an AMM pool before an account can take the pool's LPToken, the share receipt issued to liquidity providers, blocking a side door into locked assets through pool shares. Another change closes a carve-out for trust lines that already hold a balance; those lines could otherwise keep taking in locked tokens without a new approval. The other two changes tighten checks on additional send paths and limit what balances without an approval can do. Under the plan, holders would mostly only be able to send those tokens back to the issuer, and issuers could later approve the accounts and restore normal use.

Why the Gaps Matter for Large Issuers

The plan matters most for firms that issue tightly controlled assets on the XRP Ledger. Stablecoin teams and tokenized fund desks often need eligibility checks before buyers can hold their products, and tokenized funds may limit ownership to verified investors. Gaps in payment or pool flows can weaken those controls.

If locked units can move through AMM shares or older trust lines, issuer rules lose force. Closing those paths keeps the ledger's real flows in line with their intended design.

The XRP Ledger Foundation called the work routine hardening rather than a response to a live exploit, and it said it has no proof that outsiders used the gaps. Foundation lead Hussein "Vet" Zangana said known balances without an approval came from the issuers themselves or from accounts they had already approved.

fixCleanup3_5_0 Still Needs Validator Support

The four fixes remain open and are not yet in XRPL's main software. An earlier amendment placeholder for fixCleanup3_5_0 is already in the code tree, but the network cannot switch the cleanup on until the linked fixes land and validators back them — on XRPL, no single operator can activate a rule change unilaterally.

Once the changes ship in the main software, fixCleanup3_5_0 must win support from more than 80% of trusted validators, and that support must hold for two straight weeks before the amendment activates. The package also follows earlier work on locked-token rules around NFT flows; an August 2025 change closed a separate gap there, tracked in pull request no. 8174.

Progress on the rollout can be followed in the open pull requests, and activation would show up once validators begin backing the amendment on the network.

For now, the upgrade is one more step toward hardening XRPL's permission rails as controlled assets grow on the ledger. Go-live still depends on the code landing and on sustained validator support.

This article was first published by Live Bitcoin News.