# XRPL Proposal Closes a Zero-Balance Gap in Token Authorization

Published 2026-10-30 · Crypto.world Team · Crypto.world

> An open XRP Ledger proposal would block unauthorized trust lines from receiving more of an issued token, even when they already hold a balance. The change is part of fixCleanup3_5_0, which still needs to clear code review and validator voting before activation.

More than 80% of the XRP [Ledger](https://crypto.world/companies/ledger)’s trusted validators would need to support the proposed fix for two consecutive weeks before it could activate. The proposal, filed on Oct. 27 as pull request #8650, targets a gap in how the ledger checks whether an account is authorized to receive an issued token. The code remains open for review and has not taken effect on the network.

Source [github.com](https://github.com/XRPLF/rippled/pull/8650)

## The trust-line check missed accounts with balances

The XRP Ledger lets an issuer require authorization before an account can hold or receive its issued token. That control applies through a trust line, the ledger connection an account establishes to hold an asset issued by another account.

In the payment path addressed by #8650, the authorization check ran only when the trust line’s balance was exactly zero. An account that already held a balance could keep receiving the token, and a payment that crossed through zero could create an unauthorized holding of the sender’s issuance, according to the pull request.

The change would make the check apply to every attempted receipt of the issuer’s asset, rather than only to an empty trust line. An unauthorized receive would fail with `tecNO_AUTH`. If a payment tried to return more than the unauthorized balance, the flow would stop at zero instead of creating new credit; the proposal’s tests expect that excess payment to fail with `tecPATH_PARTIAL`.

## Redemption remains possible, but the line cannot grow

The proposal distinguishes receiving an issuer’s token from returning a different issuer’s IOU. An account that requires authorization can still redeem a foreign IOU, because that direction returns the destination’s own issuance rather than adding an unauthorized holding of the sender’s asset.

Existing unauthorized balances also remain spendable under the amendment description, while the test plan covers draining a balance through exact redemption and rejecting a later incoming payment. The pull request says the change leaves sending separate from the authorization rule governing who may hold and receive an asset.

The work sits within `fixCleanup3_5_0`, a proposed amendment that also includes a separate authorization check for accounts acquiring automated market maker liquidity-pool tokens. A pool token represents a claim on both assets in the pool, so the accompanying proposal checks authorization for both underlying assets when an account acquires that claim.

## The Foundation says it knows of no outsider exploit

The XRP Ledger Foundation told CoinDesk that developers were reviewing protocol guarantees, not responding to a report of affected users. “The developer discussion is about what the protocol should guarantee, not a report of affected users,” Hussein “Vet” Zangana, the Foundation’s director of community and product, told the publication.

Zangana said any unauthorized balances known to the Foundation came from payments made by issuers or accounts they had previously approved. The Foundation said it knew of no balance created by an outsider exploiting the remaining exceptions, and described the work as routine hardening rather than a response to a security incident.

## Merge and validator votes still stand between proposal and activation

Pull request #8650 is open and stacked on another pull request, #8648, which addresses authorization checks for liquidity-pool tokens. The proposal’s change therefore remains code under review, not a live rule on the XRP Ledger.

Even after the code merges and appears in a release, the amendment would need support from more than 80% of trusted validators for two consecutive weeks before activation, CoinDesk reported. Until those steps are complete, the existing authorization behavior remains in place.

## Sources

1. Original source [GitHub](https://github.com/XRPLF/rippled/pull/8650) github.com

Other pages read

2. [CoinDesk](https://www.coindesk.com/tech/2026/10/30/xrp-ledger-developers-tighten-the-rules-for-who-can-hold-restricted-tokens) coindesk.com

## Related stories

- [XRP Ledger Patch Targets Lending Bugs Before Launch](https://crypto.world/news/xrp-ledger-patch-lending-bugs-before-launch)
- [XRPL’s fixCleanup3_4_0 Slips to Nov. 4 After Vote Dip](https://crypto.world/news/xrpl-fixcleanup3-4-0-delayed-november-4-validator-vote)
- [XRPL Foundation outlines first phase of formal verification](https://crypto.world/news/xrpl-foundation-formal-verification-phase-one-scope)
- [Aviva Adds Tokenized Sterling Fund Shares to XRP Ledger](https://crypto.world/news/aviva-tokenized-sterling-fund-xrp-ledger)
- [Franklin Templeton Sends $150 Million in Fund Shares to XRP Ledger](https://crypto.world/news/franklin-templeton-150-million-xrp-ledger-sgbenji)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/xrpl-proposal-zero-balance-token-authorization-gap
