XRP Ledger developers tighten rules on who can hold 'restricted' tokens
A set of fixes closes gaps in how permissioned tokens are controlled. The XRP Ledger Foundation says no users were affected.
Developers of the XRP Ledger have proposed fixes to tighten the rules that control who can hold certain restricted tokens on the network.
What happened
The set of fixes would make it harder for tokens marked as permissioned to end up in the hands of accounts that are not approved to hold them. The XRP Ledger Foundation said no users were affected.
Background
Most crypto tokens can be sent to anyone. Permissioned or restricted tokens work differently: the issuer decides which accounts can hold them. This is important for regulated assets, such as tokenized bonds, funds or stablecoins designed for specific institutions, because issuers must often check the identity of holders and keep the asset away from sanctioned or unverified parties.
The XRP Ledger, which launched in 2012, has built-in features for issuing tokens with these kinds of controls. It is used by Ripple and others for payments and, increasingly, for tokenized real-world assets.
Why it matters
For banks and asset managers, permission controls are not optional. If a regulated token can slip to an unapproved holder, the issuer may break compliance rules, and the network becomes harder to use for serious financial products.
Fixing gaps before anyone exploits them is the best outcome. It also shows how blockchains that want institutional business must behave more like traditional financial infrastructure, with precise and enforceable rules about who can hold what.
The fixes are likely to go through the network’s usual amendment process, in which validators vote before changes take effect.
Written by Tech Security with AI assistance. Not financial advice. See our disclaimer.