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
- Version
- xrpld 3.3.0
- Enabled
- Oct 8, 2026 (UTC)
What does this amendment change?
What changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
What fee and performance figures does the specification provide?
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?
How does this amendment relate to others?
Every direct relationship has a type, an explanation and a primary source.