XRP Ledger (XRPL) Permission Delegation Nears Activation as Validator Support Holds.
The XRP Ledger is approaching activation of PermissionDelegationV1_1, an upgrade that will let accounts hand specific permissions to another account without giving away control of their main keys.
The amendment’s 14-day approval window reaches its earliest activation point at approximately 21:25 UTC today, Oct. 8.
At the latest check, it was about 14:46 UTC, leaving roughly 6 hours and 34 minutes until that threshold.
The amendment still depends on validator support remaining above the required level through the full window.
Permission Delegation Has 30 of 35 Validator Votes
The live XRPL amendment tracker showed 30 of 35 trusted validators voting yes at its latest roll call, while 29 votes are needed to keep the activation countdown running.
The current majority began on Sept. 24 at 21:25 UTC after an earlier approval period was interrupted. XRPL amendments need support from more than 80% of trusted validators for 14 consecutive days.
If support falls back to 80% or below before the timer completes, the countdown resets again.
That explains why earlier reports pointing to an Oct. 5 activation did not materialize.
The Oct. 8, 21:25 UTC mark is also not necessarily the exact second the feature turns on. Amendment votes are processed at flag ledgers, which arrive roughly every 16.5 minutes.
Based on the current ledger schedule, actual activation could occur around 21:42 UTC, provided the majority remains intact.
What Permission Delegation Changes on XRPL
PermissionDelegationV1_1 introduces a DelegateSet transaction and a corresponding Delegate ledger object.
An XRPL account will be able to authorize another account to carry out selected operations on its behalf. The delegating account keeps control of its keys while choosing exactly which functions the other account can perform.
The system supports up to 10 permissions per delegation entry, and those permissions can later be changed or revoked. Examples include allowing another account to send certain transaction types or handle narrowly defined tasks such as trust-line authorization.
This gives businesses and institutions a way to separate responsibilities. A company, for example, could let an operations account handle one type of transaction without giving it unrestricted authority over the treasury account.
This Is the Revised Version of Permission Delegation
The amendment scheduled for activation is PermissionDelegationV1_1, introduced with XRPL server version 3.3.0.
It replaces the original PermissionDelegation amendment, which was disabled after a critical bug was found. The revised version fixes that implementation while retaining the underlying XLS-75 model.
There is still one technical caution. XRPL documentation currently recommends avoiding delegation of the PaymentBurn granular permission until the separate fixCleanup3_4_0 amendment is enabled. Other granular permissions are not affected by that warning.
If validator support holds, the next milestone comes tonight: the 14-day threshold at 21:25 UTC, followed by activation at the next eligible flag-ledger sequence shortly afterward.
Be the first to comment