XRP Ledger Activates Permission Delegation Amendment

28 validator votes cleared the required threshold of 26 and enabled the PermissionDelegationV1_1 amendment on the XRP Ledger mainnet.

The XRP Ledger switched on Permission Delegation (XLS-75) on mainnet on Oct. 8, 2026. Accounts can now let another account send specific transaction types for them, without sharing keys, and revoke that at any time. NFA.

Activation Record

XRPScan recorded the activation at 21:29:50 UTC inside ledger 107524865. The amendment entered server version 3.3.0 and now lists 28 validator votes. A public server feature method already reports the feature as enabled and supported. PermissionDelegationV1_1 replaces an earlier version that had been disabled in server release 2.6.1.

New Ledger Objects

The XLS-75 specification, now marked final, introduces a Delegate ledger object and a DelegateSet transaction. A delegator issues DelegateSet to name a delegate and to list the exact permissions that delegate may exercise. The same transaction can update or revoke those permissions later.

Permission Limits

One delegator may appoint multiple delegates, each with its own permission set. Each delegate may hold up to ten permissions. Permissions can cover complete transaction types or specific granular actions defined in the amendment. Two actions remain non-delegable: changing account keys and granting further permissions to others.

Signing and Cost Rules

The delegate pays every transaction fee and signs with its own master key, regular key, or multi-signing list. The delegator never shares private keys. Each active Delegate entry adds to the delegator owner reserve. Pseudo-accounts such as automated market makers cannot serve as delegates.

Practical Use Cases

XRPL.org documentation notes that issuers can keep full-control keys offline while still approving users on authorized trust lines through a delegate. The structure supports controlled operational access without exposing master credentials. Revocation remains available at any moment through another DelegateSet transaction.

Current Status

The amendment requires no additional votes. It is now part of the live protocol and appears in the known amendments list on XRPL.org. Developers and operators can test the new DelegateSet flow against the current server release.