#8648
8648
408 views
3 Discussing
Hot
Latest
·
--
See translation
XRP Ledger devs propose fixCleanup3_5_0 to block restricted tokens from reaching unapproved accountsOPENING
Two open pull requests on the XRPL rippled repository, opened October 27, 2026, would close gaps that let tokens with issuer approval rules (RequireAuth) reach accounts the issuer never authorized; both are gated behind a new amendment, fixCleanup3_5_0. Under the first change, an account would need authorization for both assets in an AMM pool before it can acquire that pool's LP token by any route, including payments, DEX offers, NFT offers and AMM auction-slot bids.
KEY DETAILS
- Two open pull requests on the XRPL rippled repository, opened October 27, 2026, would close gaps that let tokens with issuer approval rules (RequireAuth) reach accounts the issuer never authorized; both are gated behind a new amendment, fixCleanup3_5_0.
- Under the first change, an account would need authorization for both assets in an AMM pool before it can acquire that pool's LP token by any route, including payments, DEX offers, NFT offers and AMM auction-slot bids.
- The second change closes an exemption where the payment engine's authorization check only applied when a trust line's balance was exactly zero, so an unauthorized line that already held tokens could keep receiving more.
- Neither change has been merged into rippled; fixCleanup3_5_0 is listed on the develop branch as supported with a default 'no' vote, and like any XRPL amendment it would activate only after holding more than 80% support from trusted validators for two weeks.
- The work was originally split into four pull requests; two further layers, one limiting unauthorized balances to returning funds to the issuer and a trust-line authorization invariant, were closed after review.
WHY IT MATTERS
Stablecoin and tokenized-fund issuers rely on these approval rules. (Analysis, not a confirmed fact.)
IMPORTANT CONTEXT
- Source pull requests: XRPLF/rippled #8648 and #8650, last updated October 28-29, 2026.
- This is a protocol development update, not investment advice.
- This article is informational and is not financial advice. Digital assets are volatile.
SOURCE
- Primary / main source: https://x.com/CoinDesk/status/2116112415096242286
- Supporting: https://github.com/XRPLF/rippled/pull/8648
- Supporting: https://github.com/XRPLF/rippled/pull/8650
- Supporting: https://github.com/XRPLF/rippled/blob/develop/include/xrpl/protocol/detail/features.macro
- Supporting: https://xrpl.org/docs/concepts/networks-and-servers/amendments
- Supporting: https://www.coindesk.com/tech/2026/10/30/xrp-ledger-developers-tighten-the-rules-for-who-can-hold-restricted-tokens
#XRP #XRPL
XRP Ledger devs propose fixCleanup3_5_0 to block restricted tokens from reaching unapproved accounts
OPENING
Two open pull requests on the XRPL rippled repository, opened October 27, 2026, would close gaps that let tokens with issuer approval rules (RequireAuth) reach accounts the issuer never authorized; both are gated behind a new amendment, fixCleanup3_5_0. Under the first change, an account would need authorization for both assets in an AMM pool before it can acquire that pool's LP token by any route, including payments, DEX offers, NFT offers and AMM auction-slot bids.
KEY DETAILS
- Two open pull requests on the XRPL rippled repository, opened October 27, 2026, would close gaps that let tokens with issuer approval rules (RequireAuth) reach accounts the issuer never authorized; both are gated behind a new amendment, fixCleanup3_5_0.
- Under the first change, an account would need authorization for both assets in an AMM pool before it can acquire that pool's LP token by any route, including payments, DEX offers, NFT offers and AMM auction-slot bids.
- The second change closes an exemption where the payment engine's authorization check only applied when a trust line's balance was exactly zero, so an unauthorized line that already held tokens could keep receiving more.
- Neither change has been merged into rippled; fixCleanup3_5_0 is listed on the develop branch as supported with a default 'no' vote, and like any XRPL amendment it would activate only after holding more than 80% support from trusted validators for two weeks.
- The work was originally split into four pull requests; two further layers, one limiting unauthorized balances to returning funds to the issuer and a trust-line authorization invariant, were closed after review.
WHY IT MATTERS
Stablecoin and tokenized-fund issuers rely on these approval rules. (Analysis, not a confirmed fact.)
IMPORTANT CONTEXT
- Source pull requests: XRPLF/rippled #8648 and #8650, last updated October 28-29, 2026.
- This is a protocol development update, not investment advice.
- This article is informational and is not financial advice. Digital assets are volatile.
SOURCE
- Primary / main source: https://x.com/CoinDesk/status/2116112415096242286
- Supporting: https://github.com/XRPLF/rippled/pull/8648
- Supporting: https://github.com/XRPLF/rippled/pull/8650
- Supporting: https://github.com/XRPLF/rippled/blob/develop/include/xrpl/protocol/detail/features.macro
- Supporting: https://xrpl.org/docs/concepts/networks-and-servers/amendments
- Supporting: https://www.coindesk.com/tech/2026/10/30/xrp-ledger-developers-tighten-the-rules-for-who-can-hold-restricted-tokens
#XRP #XRPL
Two open pull requests on the XRPL rippled repository, opened October 27, 2026, would close gaps that let tokens with issuer approval rules (RequireAuth) reach accounts the issuer never authorized; both are gated behind a new amendment, fixCleanup3_5_0. Under the first change, an account would need authorization for both assets in an AMM pool before it can acquire that pool's LP token by any route, including payments, DEX offers, NFT offers and AMM auction-slot bids.
KEY DETAILS
- Two open pull requests on the XRPL rippled repository, opened October 27, 2026, would close gaps that let tokens with issuer approval rules (RequireAuth) reach accounts the issuer never authorized; both are gated behind a new amendment, fixCleanup3_5_0.
- Under the first change, an account would need authorization for both assets in an AMM pool before it can acquire that pool's LP token by any route, including payments, DEX offers, NFT offers and AMM auction-slot bids.
- The second change closes an exemption where the payment engine's authorization check only applied when a trust line's balance was exactly zero, so an unauthorized line that already held tokens could keep receiving more.
- Neither change has been merged into rippled; fixCleanup3_5_0 is listed on the develop branch as supported with a default 'no' vote, and like any XRPL amendment it would activate only after holding more than 80% support from trusted validators for two weeks.
- The work was originally split into four pull requests; two further layers, one limiting unauthorized balances to returning funds to the issuer and a trust-line authorization invariant, were closed after review.
WHY IT MATTERS
Stablecoin and tokenized-fund issuers rely on these approval rules. (Analysis, not a confirmed fact.)
IMPORTANT CONTEXT
- Source pull requests: XRPLF/rippled #8648 and #8650, last updated October 28-29, 2026.
- This is a protocol development update, not investment advice.
- This article is informational and is not financial advice. Digital assets are volatile.
SOURCE
- Primary / main source: https://x.com/CoinDesk/status/2116112415096242286
- Supporting: https://github.com/XRPLF/rippled/pull/8648
- Supporting: https://github.com/XRPLF/rippled/pull/8650
- Supporting: https://github.com/XRPLF/rippled/blob/develop/include/xrpl/protocol/detail/features.macro
- Supporting: https://xrpl.org/docs/concepts/networks-and-servers/amendments
- Supporting: https://www.coindesk.com/tech/2026/10/30/xrp-ledger-developers-tighten-the-rules-for-who-can-hold-restricted-tokens
#XRP #XRPL
39
·
--
Verified
XRPL proposes tightening token receiving permissions: read the word “proposes” carefully
On October 30, a check of the rippled code repository showed that proposals #8648 and #8650 were still open and had not been merged
The focus is on tokens whose issuers require holders to be authorized:
• When receiving tokens representing a share of an AMM pool, an account must be authorized for both assets in the pool
• A trust line with an existing balance must also be checked for permission to receive additional tokens, rather than being exempt from the check simply because its balance is nonzero
A trust line can be understood as an account relationship established to hold an issuer’s token on the XRPL
Both changes use the fixCleanup3_5_0 amendment. The current code description also says that two other checks were closed after review; so I wouldn’t read the summary as “four fixes have been deployed”
Notably, XRPL documentation explicitly states that this mechanism for authorizing holders does not apply to native XRP
In my view, the issue here is whether rules for assets issued on-chain can be enforced consistently. If a token requires recipients to be approved, transfer routes through pools should also comply with that condition
The review process, release, and actual activation still need to be monitored. Code that is still being proposed is not yet an effective rule on mainnet
What do you think: should tokenized institutional assets prioritize free transferability or control over who is allowed to hold them?
Sources: XRPLF/rippled PR #8648, #8650; XRPL documentation “Authorized Trust Lines,” checked on October 30, 2026
$XRP
XRPL proposes tightening token receiving permissions: read the word “proposes” carefully
On October 30, a check of the rippled code repository showed that proposals #8648 and #8650 were still open and had not been merged
The focus is on tokens whose issuers require holders to be authorized:
• When receiving tokens representing a share of an AMM pool, an account must be authorized for both assets in the pool
• A trust line with an existing balance must also be checked for permission to receive additional tokens, rather than being exempt from the check simply because its balance is nonzero
A trust line can be understood as an account relationship established to hold an issuer’s token on the XRPL
Both changes use the fixCleanup3_5_0 amendment. The current code description also says that two other checks were closed after review; so I wouldn’t read the summary as “four fixes have been deployed”
Notably, XRPL documentation explicitly states that this mechanism for authorizing holders does not apply to native XRP
In my view, the issue here is whether rules for assets issued on-chain can be enforced consistently. If a token requires recipients to be approved, transfer routes through pools should also comply with that condition
The review process, release, and actual activation still need to be monitored. Code that is still being proposed is not yet an effective rule on mainnet
What do you think: should tokenized institutional assets prioritize free transferability or control over who is allowed to hold them?
Sources: XRPLF/rippled PR #8648, #8650; XRPL documentation “Authorized Trust Lines,” checked on October 30, 2026
$XRP
On October 30, a check of the rippled code repository showed that proposals #8648 and #8650 were still open and had not been merged
The focus is on tokens whose issuers require holders to be authorized:
• When receiving tokens representing a share of an AMM pool, an account must be authorized for both assets in the pool
• A trust line with an existing balance must also be checked for permission to receive additional tokens, rather than being exempt from the check simply because its balance is nonzero
A trust line can be understood as an account relationship established to hold an issuer’s token on the XRPL
Both changes use the fixCleanup3_5_0 amendment. The current code description also says that two other checks were closed after review; so I wouldn’t read the summary as “four fixes have been deployed”
Notably, XRPL documentation explicitly states that this mechanism for authorizing holders does not apply to native XRP
In my view, the issue here is whether rules for assets issued on-chain can be enforced consistently. If a token requires recipients to be approved, transfer routes through pools should also comply with that condition
The review process, release, and actual activation still need to be monitored. Code that is still being proposed is not yet an effective rule on mainnet
What do you think: should tokenized institutional assets prioritize free transferability or control over who is allowed to hold them?
Sources: XRPLF/rippled PR #8648, #8650; XRPL documentation “Authorized Trust Lines,” checked on October 30, 2026
$XRP
1
838
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number
Trending Topics
1
#HeYiSaysWithdrawalsExpectedtoResumeWithin42Hours
48,988 views
887 Discussing
2
#CZSaysCompensationIsinPlaceUsersAreProtected
54,708 views
743 Discussing
3
#RichardTengSaysBinanceWillCoverAllHackedLosseswithCompanyFunds
8,682 views
53 Discussing
4
#IntelHasItsWorstDaySince1974
10,470 views
296 Discussing
5
#TRMCambodianCasinosReceived$1.07BInCrypto
2,000 views
53 Discussing
6
#USDCCirculationFallsAbout800MInSevenDays
29,801 views
470 Discussing
7
#SuspectedNorthKoreaAttacksAccountForNearly89%OfCryptoHackLosses
9,304 views
77 Discussing
8
#OpenAICutsFundraisingTargetBy$10B
2,091 views
61 Discussing
9
#ASICHasReceivedNoPredictionMarketApplications
41,913 views
889 Discussing
10
#RecallAnnouncesLiquidationPlansToBurn35.86%OfSupply
730 views
24 Discussing