XRP Ledger validators have put PermissionDelegationV1_1 into its activation window, with October 5 reported as the earliest activation date if support remains above the required threshold. The feature lets one account authorize another account to perform a limited set of actions without handing over the owner's main key. CoinDesk, XRPL amendment process.
The distinction is scope. A delegate can sign transactions as the account owner only when the transaction matches permissions recorded in a Delegate ledger entry. Permission sets can cover transaction types or narrower functions, allowing an organization to separate duties such as payments and compliance operations.
Delegation is not unrestricted account control. XRPL documentation says one delegate can receive at most 10 permissions, some sensitive permissions cannot be delegated, and delegated transactions cannot wait in the ordinary transaction queue. Each Delegate entry also counts toward the owner's reserve. Permission delegation documentation.
The version number matters. The original PermissionDelegation amendment was disabled after a critical bug and replaced by PermissionDelegationV1_1. Operators need software that understands the replacement amendment, while users should wait for confirmed activation and wallet support before treating the feature as available. Validator support and a countdown indicate protocol readiness work, not adoption by banks and not a price signal for XRP.