Skip to content
EnabledTier BIdentity & Oracles

PermissionDelegationV1_1 XLS-75

Accounts can delegate selected transaction permissions to other accounts while keeping their own keys private. PermissionDelegationV1_1 is enabled on the XRP Ledger. xrpscan reports Oct 8, 2026 (UTC) as its activation date and xrpld 3.3.0 as its first version.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Enabled
XLS
XLS-75
Enabled
Oct 8, 2026 (UTC)

What does this amendment change?

Why does this amendment exist?

Issuers and businesses want to distribute operational tasks such as token issuance or trust line approval among several people while retaining full account control. The first version was disabled after a bug, so the feature returns under a new amendment ID.

How does the mechanism work?

DelegateSet creates a Delegate object for a pair of accounts with up to ten permissions; an empty list deletes it. The delegate submits transactions with the Delegate field, signs with its own keys, and pays the fee, while only the delegating account's Sequence increases. Granular permissions allow only the transaction fields and flags defined for that permission.

What changes compared with the predecessor?

BeforeAfter
Account actions such as authorizing trust lines required direct control over the account's keys. The first version, PermissionDelegation, has been marked unsupported since rippled 2.6.1.With the amendment enabled, an account can assign selected transaction types or granular permissions such as TrustlineAuthorize to individual other accounts, then replace or delete that list at any time.

Who is this change relevant to?

XRP holders and users

Delegation is voluntary. Delegating a permission such as Payment gives the delegate access to the corresponding funds, so grants should be narrowly scoped.

Wallets and app developers

Wallets must recognize the Delegate field, attribute the fee to the delegate, and clearly show which permissions an account has granted.

Exchanges and issuers

Issuers can separate roles such as token issuance, trust line administration, and KYC approvals performed by an external provider.

Node operators

For every delegated transaction, nodes check the relevant Delegate object, the permission, and the permitted fields and flags for granular permissions.

What limitations and risks remain?

  • Until fixCleanup3_4_0 is enabled, xrpl.org recommends against delegating PaymentBurn: in certain cases, that permission can also mint trust line tokens or MPTs. Other granular permissions are not affected by this issue.
  • The complete AccountSet, SetRegularKey, SignerListSet, DelegateSet, and AccountDelete transactions cannot be delegated.
  • Vault and lending transactions, SponsorshipTransfer, and ConfidentialMPTConvert are also excluded.
  • A Delegate object stores at most ten permissions.
  • Permissions cannot be granted to a pseudo-account.
  • From xrpld 3.3.0, delegated transactions are not admitted to the transaction queue.

What fee and performance figures does the specification provide?

  • The delegate pays the delegated transaction's fee.
  • Each Delegate object requires an object reserve from the delegating account.
Technical details: transactions, fields, codes and invariants

Transactions

  • DelegateSet
  • delegable transactions with the Delegate field

Ledger objects

  • Delegate

Fields and flags

  • Authorize
  • Permissions (at most 10 entries)
  • Delegate (common transaction field)

API methods

  • account_tx (delegated-transaction filter from xrpld 3.3.0)

Result codes

  • temDISABLED
  • temARRAY_TOO_LARGE
  • temMALFORMED
  • temBAD_SIGNER
  • tecNO_TARGET
  • tecPSEUDO_ACCOUNT
  • tecNO_ENTRY
  • terNO_DELEGATE_PERMISSION

Invariants

  • An account cannot submit a transaction on another account's behalf without a valid Delegate object.

What does a concrete workflow look like?

An issuer grants a KYC service provider only the granular TrustlineAuthorize permission. The provider can approve trust lines but cannot make payments from the issuer's account.

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

replaces

PermissionDelegation

PermissionDelegationV1_1 replaces the first delegation version, disabled in rippled 2.6.1, and according to xrpl.org fixes a critical bug in the original implementation.

Check the relationship in the primary source

What happens next for this amendment?

PermissionDelegationV1_1 is enabled on the XRP Ledger. xrpscan reports Oct 8, 2026 (UTC) as its activation date and xrpld 3.3.0 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

Where does it sit within its amendment family?

AMM and Clawback: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. AMMEnabled · from rippled 1.12.0
  5. ClawbackEnabled · from rippled 1.12.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixInnerObjTemplateEnabled · from rippled 2.1.0
  8. fixAMMOverflowOfferEnabled · from rippled 2.1.1
  9. fixAMMv1_1Enabled · from rippled 2.2.0
  10. fixPreviousTxnIDEnabled · from rippled 2.2.0
  11. AMMClawbackEnabled · from rippled 2.3.0
  12. fixAMMv1_2Enabled · from rippled 2.3.0
  13. fixInnerObjTemplate2Enabled · from rippled 2.3.0
  14. fixFrozenLPTokenTransferEnabled · from rippled 2.4.0
  15. DeepFreezeEnabled · from rippled 2.4.0
  16. PermissionedDEXEnabled · from rippled 2.5.0
  17. fixAMMv1_3Enabled · from rippled 2.5.0
  18. PermissionDelegationDeprecated · from rippled 2.5.0
  19. fixAMMClawbackRoundingEnabled · from rippled 3.0.0
  20. SponsorOpen for voting · from xrpld 3.3.0
  21. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  22. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  23. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  24. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications