XRP Ledger developers have put forward a set of four protocol amendments, grouped under the fixCleanup3_5_0 amendment, to close identified gaps in the network’s issuer‑approval enforcement for restricted tokens. The proposals aim to ensure that assets such as regulated stablecoins or tokenized funds retain consistent approval requirements across all transaction pathways, including automated market maker (AMM) pool shares, direct payments, and NFT offers. According to the XRP Ledger Foundation, the work is a routine hardening of the protocol and not a response to any external security breach.

Strengthening checks on AMM pool shares

One of the four fixes focuses on liquidity‑provider (LP) tokens that represent a claim on the assets held inside an AMM pool. Currently, an account must be authorized for the underlying assets before it can deposit into a pool, but the LP token itself could be transferred via other routes without triggering the same approval check. The new rule would require an account to hold the necessary issuer authorization for both assets in the pool before it can acquire the corresponding LP token, extending the check to payments, trading offers, and NFT offers involving LP tokens. This prevents a bypass of approval requirements through indirect acquisition of pool shares.

Blocking unauthorized token inflows on existing balances

A second proposal addresses an exception where trust lines that already hold a restricted token can continue receiving additional units even if the account lacks current approval. The existing logic only performed an authorization check when the trust line’s balance was zero. The amendment would enforce the approval requirement regardless of the existing balance, stopping unauthorized accounts from accumulating more restricted tokens via subsequent transfers.

Consistent enforcement across the ledger

The remaining two fixes aim to align the approval logic across both current and future XRP Ledger features, ensuring that any new mechanisms inherit the same strict checks. For accounts that already possess restricted tokens without proper approval, the proposals would generally allow those tokens to be returned to the issuer, after which the issuer could re‑authorize the trust line if desired. The foundation noted that known unauthorized balances stemmed from issuer‑initiated payments or previously approved accounts, not from outside exploitation.

Implementation path and next steps

As of the October 30 report, none of the four fixes have been merged into the mainnet software. Adoption will require the changes to be incorporated into the validator client code and to receive continuous support from the network’s trusted validators for at least two weeks. This validator approval process mirrors that of other upcoming upgrades, such as the XRP Ledger Batch upgrade. If the fixes are eventually activated, issuers will gain more reliable tools to enforce eligibility requirements, while holders will need to ensure their accounts maintain the necessary authorizations to retain or receive restricted assets.