The XRP Ledger is lining up another major protocol upgrade, with PermissionDelegationV1_1 potentially activating on Oct. 5 if validator support remains above the network’s required threshold.
The amendment entered its 14-day activation period after 29 of 35 trusted validators backed it, according to the live amendment data cited by Crypto.news. At least 28 validators must continue supporting the change for activation to proceed.
The underlying feature is documented by the official XRP Ledger documentation, which describes permission delegation as a way for one account to grant another account specific authority without handing over complete control.
What Permission Delegation Actually Changes
PermissionDelegationV1_1 introduces more granular account control.
Instead of giving another system or employee access to an account’s full signing authority, an XRPL account could authorize specific actions while keeping other capabilities restricted.
For example, a business could allow an operational account to execute payments without letting it change the primary account’s keys. A stablecoin issuer could similarly separate compliance operations from custody of its most sensitive credentials.
XRPL documentation says delegated permissions can cover transaction types as well as more narrowly defined functions.
That structure is particularly relevant as the ledger expands into institutional finance. XRPL already hosts growing volumes of tokenized real-world assets, while projects such as institutional-grade lending are increasing the need for more sophisticated account controls.
Oct. 5 Is Conditional, Not Guaranteed
The Oct. 5 date is not fixed.
XRPL amendments generally need more than 80% validator support for two consecutive weeks before they activate. Coinpaper recently explained how XRPL amendments and validator voting actually work.
If support for PermissionDelegationV1_1 drops below the required threshold before the countdown ends, the activation timer would reset.
The amendment is also a replacement for an earlier PermissionDelegation proposal that was disabled after a critical bug was discovered. The revised V1_1 implementation was included in xrpld 3.3.0, alongside BatchV1_1, ConfidentialTransfer, DynamicMPT and Sponsor.
