XRP Ledger activates delegated permission functionality, supporting the separation of payment and compliance functions

On October 8, the XRP Ledger activated the PermissionDelegationV1_1 feature, allowing account owners to authorize other accounts to perform specific tasks without relinquishing control of the account's master key. According to the monitoring site XRPL Dashboard, such upgrades require over 80% support from trusted validators for two consecutive weeks; based on the current 35 validators, at least 29 must support it. The countdown for this feature was reset in September due to the support rate falling below the threshold.

This feature allows enterprises to split permissions by function. Stablecoin issuers can authorize compliant accounts to approve new customers while keeping the master key offline. Authorized accounts use their own keys to sign and can only perform the granted operations; owners can change or revoke these permissions at any time. Each authorized account can receive up to 10 permissions, which limit the types of operations they can perform, rather than automatically setting spending limits. Banks have previously separated payment and compliance responsibilities at the employee level, and this upgrade enforces such division at the ledger level.

According to a report shared by Evernorth, a subsidiary of XRP Treasury, the network held an average of $3.72 billion in tokenized assets and $539 million in Ripple's RLUSD stablecoin in the second quarter, totaling approximately $4.26 billion. Official guidance advises users not to delegate PaymentBurn permissions before separately fixing activation; this permission is intended for assistants to destroy tokens but, under certain conditions, also allows for the creation of new tokens. This warning pertains to tokens issued on the ledger rather than newly minted XRP.