XRP Ledger Developers Must Settle 2 Token-Approval Amendments Before Mainnet
Key Takeaways
- •PR #8648 and PR #8650 address the XRP Ledger’s handling of issuer-authorized tokens.
- •The proposals remain outside the mainnet’s active rules, leaving the current approval process unchanged.
- •Issued tokens other than XRP are transferred through trust lines connecting issuers and holders.
- •Each amendment requires approximately 80% validator support maintained for about two weeks to activate.
- •No decision had been reached on either proposal as of the publication date.
The XRP Ledger's developer community still owes the network a decision on two amendment proposals that harden how accounts receive tokens whose issuers demand approval — and neither change has yet been written into the mainnet's rules.
The pair, filed as PR #8648 and PR #8650 in the XRP Ledger Foundation's server software, remains pending. According to a November 2, 2026 report by COINOTAG, the amendments would tighten the protocol's handling of tokens that require issuer authorization before an account can hold them. That pending status has a concrete consequence for issuers and holders of authorization-gated tokens: the approval pathway keeps operating under the ledger's current rules until validators actually adopt the changes.
What the proposals cover
On the XRP Ledger, issued tokens — assets other than the network's native XRP — move along 'trust lines' that link an issuer to each holder. Issuers can enable a setting that requires a holder to be approved before the token can be delivered to them, a mechanism commonly used for assets subject to compliance or access-control requirements. The two proposals target this approval pathway, strengthening the rules that govern how accounts receive such tokens.
The path to mainnet activation
Changes to the XRP Ledger's core behavior are adopted through its amendment system. Proposed changes ship in the server software, and network validators signal support for each amendment. A change becomes part of the live protocol only after a supermajority of validators — roughly 80 percent — sustains support over a period of about two weeks. Until that threshold is reached, code present in a repository does not automatically become ledger rules, which is why PR #8648 and PR #8650 can sit in the codebase without yet governing the mainnet. For observers, the practical signal to track is validator voting: as new releases ship, each proposal advances only if support reaches and holds at the roughly 80 percent threshold for the two-week window; until then it stays outside the ledger's active rule set.
As of publication, no decision has been reached on either proposal, and developers must still settle the question before either amendment can take effect on the mainnet.
This article is based on source content first published on COINOTAG: https://en.coinotag.com/xrp-ledger-token-approval-amendments-review
