The XRP Ledger activated PermissionDelegationV1_1 at ledger 107,524,865 on 8 October, enabling account owners to grant limited transaction authority to separate accounts without exposing the keys that control their primary holdings.
The feature supports role-based access controls. A stablecoin issuer, for example, can authorize an operational account to approve customer trust lines while keeping master authority offline. A delegator can maintain multiple delegates, with each receiving as many as 10 defined permissions.
The official XRP Ledger documentation says delegates cannot change the delegator’s keys or grant further permissions. Delegated transactions also cannot wait in the transaction queue, and the permission model limits actions by type rather than by a custom spending ceiling.
One warning remains active. Until fixCleanup3_4_0 is enabled, the documentation recommends against delegating the PaymentBurn permission because the delegate may be able to mint fungible tokens in certain circumstances. Other granular permissions are not described as affected.
TOKEN RECON ASSESSMENT
Delegation gives institutions a practical separation between cold authority and online operations, but it is not unrestricted policy control. The absence of customizable amount limits and the PaymentBurn warning require conservative deployment. Production evidence will come from identifiable issuers using delegates safely, not from amendment activation alone.
Sources
XRP Ledger, Permission Delegation documentation
