Skip to content
News
LiveUnited States

XRP Ledger activates PermissionDelegationV1_1, splitting operational and compliance keys for institutions


Key points

  • PermissionDelegationV1_1 activated on the XRP Ledger on 8 October after clearing the network's 80% validator threshold, which requires at least 29 of 35 trusted validators for two consecutive weeks.
  • The feature allows account owners to grant other accounts up to 10 granular, action-scoped permissions without sharing primary signing keys, enabling enforceable separation of payment and compliance functions on-chain.
  • Developers have issued an explicit advisory against delegating the PaymentBurn permission until a separate fix activates, because a flaw currently allows helper accounts to create issued tokens rather than only destroying them.
  • The PaymentBurn fix held 27 of 35 validator votes as of Friday, 8 October, still two votes short of the 29 needed to begin its own two-week ratification countdown.
  • Evernorth reported that the XRP Ledger held an average of $3.72 billion in tokenised assets and $539 million in RLUSD during Q2, a combined balance of approximately $4.26 billion, illustrating the institutional scale the upgrade is designed to serve.

The XRP Ledger activated PermissionDelegationV1_1 on 8 October, enabling account owners to authorise separate accounts to carry out specific tasks without exposing the primary signing keys that control their main holdings. The upgrade passed after clearing the network’s threshold of support from at least 29 of 35 trusted validators over two consecutive weeks, a countdown that had to restart in September after backing slipped below that level.

The practical architecture the feature enables mirrors the internal controls banks already apply to staff: a stablecoin issuer, for instance, can allow a compliance account to onboard customers while keeping its master keys air-gapped, and a payments account can settle transactions without any visibility into the broader treasury. Each delegated account can hold up to 10 granular permissions, scoped by action type rather than by a spending cap, and the owner retains the ability to amend or revoke those grants at any time.

One active caveat requires operator attention. Developers have warned against delegating the PaymentBurn permission until a separate amendment activates to close a flaw that, under certain conditions, allows a helper account to create issued tokens rather than only destroying them. That fix held 27 of 35 validator votes as of Friday, two short of the 29 needed to start the two-week ratification countdown. A second, unrelated bug affecting how some servers count validator support during amendment votes is also under review; a proposed patch would anchor validator identity to a permanent identifier rather than a rotating security key.

Context on the ledger’s institutional footprint comes from a report by Evernorth, an XRP treasury company, which recorded an average of $3.72 billion in tokenised assets and $539 million in Ripple’s RLUSD stablecoin on the network during the second quarter, for a combined balance of roughly $4.26 billion. The delegation feature is directly relevant to the operational models of the institutions managing assets at that scale.

Original source

Coindesk Markets desk

coindesk.com