XRP Ledger's proposed fixes check who may receive the contents of a pool.

Current development check: two XRP Ledger pull requests opened on 27 October remain under review. They propose tighter authorisation checks for liquidity-pool tokens and trust lines carrying existing balances. Open code proposals are not activated mainnet rules.

A liquidity-provider token represents a claim on the assets inside an automated market-making pool. Pull request 8648 argues that checking permission only when someone deposits into the pool leaves gaps when that claim later changes hands. Its proposed checks cover receipt through payments, offers and other paths, requiring permission for both underlying pool assets.

Pull request 8650 addresses another edge case: an unauthorised trust line with a residual balance continuing to receive more. The proposed change would prevent that balance growing while retaining routes for returning assets. The repository describes both changes as gated by an amendment, rather than unconditional alterations to every live ledger.

The practical interest is in issuer-controlled assets and the consistency of their permissions across trading features. It is not a new XRP token, an announced exploit loss or a prediction about XRP's price. Both requests still show open review, so users and developers should follow implementation and activation separately. This is a clearly labelled development feature, not breaking launch news.