Key Highlights
- Ripple’s RLUSD team is testing Permission Delegation on the XRPL Devnet, with the feature currently subject to validator voting on the XRP Ledger.
- The feature allows an issuer to assign specific functions to separate accounts while keeping the primary account keys in cold storage.
- For RLUSD, permissions could be divided among teams, with compliance handling freeze and clawback, operations managing mint and burn, and KYC providers handling trust line authorization.
The RLUSD team at Ripple is building and testing the feature on the XRPL Devnet known as “Permission Delegation,” which is currently under validator voting on the XRP Ledger.
In an X post on Friday, an XRP Ledger dUNL validator states that the feature allows an account holder to assign specific, limited functions to other accounts. The primary account’s keys can remain in cold storage while authorized secondary accounts carry out only the designated tasks.
How Permission Delegation works
Lauren Betra, the stablecoin product lead at Ripple, gave further context and stated that, on the XRP Ledger, a token issuer account currently controls core functions such as minting, freezing, clawback, and trust line authorization. For regulated issuers, these responsibilities are typically divided among different internal teams, including compliance, operations, and security. Permission Delegation is structured to support that division of labor.
An issuer can grant individual permissions to separate accounts. In one described configuration for the RLUSD issuer account, the compliance team receives freeze and clawback authority, the operations team receives mint and burn authority, and a KYC provider receives trust line authorization authority. Each team operates with its own account keys while acting on the main RLUSD issuer account. The issuer account’s primary key remains offline.
Distinction from multisignature arrangements
Permission Delegation differs from multisignature (multisig) setups. Multisig requires multiple parties to approve a single transaction. Delegation authorizes a specific account to perform a defined action on behalf of the issuer.
One approach divides approval authority; the other divides operational responsibilities. Certain account-level permissions cannot be delegated. This restriction prevents delegates from expanding their own access rights. The issuer retains the ability to grant or revoke permissions at any time.
The feature is intended for use by institutions issuing regulated assets on the XRP Ledger. Stablecoin issuers, real-world asset tokenizers, and asset managers that bring regulated instruments on-chain often require separation between teams responsible for moving assets, enforcing compliance rules, and managing security.
Permission Delegation provides a protocol-level mechanism to implement that separation. The same structure can apply to other regulated tokens beyond RLUSD. Parallel development and testing by the RLUSD team continue on the XRPL Devnet.
Related infrastructure developments
On August 21, 2026, Ankr introduced RPC infrastructure for the XRP Ledger. The service supports enterprise and developer connections within the Ripple ecosystem, which includes more than 300 financial institutions engaged in cross-border payments across Asia, the Middle East, Latin America, and other regions.
The combination of protocol-level features such as Permission Delegation and supporting infrastructure services forms part of the current technical environment available to institutions operating on the XRP Ledger.
Also Read: Sky Beats Major Issuers in Tokenized Funds Market Cap
