XRP Ledger New Feature Enters Voting, May Improve RLUSD Issuance Management

icon币界网
Share
AI summary iconSummary
Lauren Berta from Ripple announced that a new token listing feature called "authorized delegation" for the XRP Ledger is now in validator voting. Part of xrpld 3.3.0, the feature enables RLUSD and other tokens to delegate operations such as minting, freezing, and KYC checks to separate accounts, supporting institutional adoption by aligning token management with enterprise workflows. The RLUSD team is preparing a testnet, with a circulating supply now exceeding $2 billion.
CoinMarketCap reports:

Lauren Berta, Head of Ripple’s Stablecoin Product, said that a new feature on the XRP Ledger called "Delegated Permissions" has entered the validator voting phase. If approved and enabled, this feature will bring the issuance, risk management, and permission controls of RLUSD and other regulated tokens on-chain closer to the existing operational workflows of institutions.

New feature has entered voting

This feature comes from the xrpld 3.3.0 release earlier this month, which introduced XLS-75, a more granular account permission delegation mechanism.

According to Ripple, token issuance accounts on the XRPL currently control several key operations, including minting, freezing, reclaiming, and trust line authorization. For regulated issuers, these functions are typically managed by separate teams responsible for compliance, operations, and security.

Different teams can be executed separately.

The design goal of permission delegation is to allow the issuer to assign specific operations to different accounts without relinquishing control of the main account, while reducing the risk of exposing the core account directly.

  • The compliance team can be responsible for freezing and recovering assets.
  • The operations team can be responsible for minting and burning.
  • KYC service providers can handle trust line authorization.

Each team can complete their respective tasks using their own keys, without needing to share the same issuing account.

Different from multi-signature use cases

Berta also emphasized that permission delegation is not the same as multi-signature. Multi-signature focuses on requiring multiple parties to jointly approve a transaction, while permission delegation allows one account to perform specific actions on behalf of another account.

She summarized the distinction between the two as follows: the former decentralizes approval authority, while the latter decentralizes responsibilities. For stablecoin issuers, RWA tokenization entities, and asset managers moving regulated assets onto the blockchain, the latter is better suited for scenarios requiring parallel management of team分工, compliance execution, and security protocols.

This feature is currently under review in the XRPL validator voting process. Meanwhile, the RLUSD team is developing and testing the necessary capabilities on the testnet to prepare for future enablement.

Additional information: The circulating supply of Ripple USD (RLUSD) has surpassed $2 billion, and its native governance capabilities on the XRPL will be further enhanced if permission delegation is eventually launched.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.