How Can XRP Ledger Delegation Separate Issuer Roles?
XRP Ledger activated the PermissionDelegationV1_1 amendment on October 8, allowing an account to authorize another account for selected transaction types without sharing its own signing keys. For token issuers, this can separate routine functions such as customer approval from control of the main treasury account.
TL;DR — Key Takeaways
- ✓Activation: PermissionDelegationV1_1 went live on XRP Ledger on October 8.
- ✓Control: Owners can authorize delegates for selected transaction permissions.
- ✓Key safety: Delegates sign with their own keys; owners retain primary account keys.
- ✓Limit: Permissions limit transaction types, not necessarily spending amounts.
Delegation Separates Duties at the Account Level
The PermissionDelegationV1_1 amendment activated on XRP Ledger on October 8. Under the feature, an account owner can authorize another account to submit selected transactions using the delegate’s own signing key.
That can let a stablecoin issuer authorize an operations account to approve customers or handle a limited class of transactions, while keeping the primary account’s keys under separate control. The owner can update or remove the delegated permissions.
XLS-75 describes delegation as a way to grant narrowly scoped, revocable permissions without handing over full account authority.
— XRP Ledger Standard XLS-75; activation reported October 8, 2026
The implementation moves some segregation of duties from internal policy into ledger-enforced permissions, but it does not replace a key-management program or approval workflow.
Permission Scope Is Not a Spending Cap
The standard allows an owner to grant up to ten permissions to a delegate. Those permissions restrict which transaction categories are available, but do not automatically set a maximum value for a payment or establish a business-specific approval threshold.
The standard also contains important safety limits and cautions. In particular, its current text recommends not delegating the PaymentBurn granular permission until a separate amendment fix is active, because of a token-minting issue under specific circumstances.
Issuers must therefore review each permission, the delegate’s signing controls and ledger amendment status before using the feature in production operations.
Frequently Asked Questions
What changed on XRP Ledger on October 8?
The PermissionDelegationV1_1 amendment activated, allowing accounts to grant selected transaction permissions to other accounts.
Does delegation give another account the owner’s private keys?
No. The delegate uses its own keys and can perform only the transaction types or granular permissions granted by the owner.
Does the feature impose a spending limit?
Not automatically. The permissions constrain kinds of actions; they are not, by themselves, a spending cap.
Is every permission safe to delegate?
No. The XRPL standard warns that some permissions can enable sensitive actions, and specifically advises against delegating PaymentBurn until a separate fix activates.