Ripple’s RLUSD team is building and testing Permission Delegation on the XRPL Devnet while validators vote on whether to activate the feature on the XRP Ledger. Version 3.3.0 of xrpld, the reference server implementation for the protocol, introduced XLS-75, titled "PermissionDelegationV1_1: Granular account Permission Delegation." The feature would let an issuer assign narrowly defined functions to separate accounts while keeping the primary account keys in cold storage. For RLUSD, compliance could control freezing and clawbacks, operations could handle minting and burning, and a KYC provider could authorize trust lines. Unlike multisignature arrangements, which require several parties to approve one transaction, delegation assigns a defined action to a specific account. Account-level permissions that could expand a delegate’s access cannot be delegated, while the issuer can grant or revoke permissions at any time. Ripple stablecoin product lead Lauren Berta said the design could help regulated issuers divide responsibilities among compliance, operations, security and other teams at the protocol level. The same model could serve stablecoin issuers, real-world asset tokenizers and asset managers issuing regulated tokens on XRPL. RLUSD’s total circulating supply has surpassed $2 billion. Separately, Ankr introduced XRP Ledger RPC infrastructure on August 21, 2026, supporting enterprise and developer connections within the Ripple ecosystem, which includes more than 300 financial institutions involved in cross-border payments across Asia, the Middle East, Latin America and other regions.