XRPL’s revised PermissionDelegationV1_1 amendment entered its 14-day activation countdown on September 21 after gaining support from 29 of the network’s 35 trusted validators. The upgrade is
XRPL’s revised PermissionDelegationV1_1 amendment entered its 14-day activation countdown on September 21 after gaining support from 29 of the network’s 35 trusted validators. The upgrade is projected to activate on October 5, provided that backing remains above the required threshold throughout the waiting period, according to CoinDesk.
The countdown marks a second attempt to deploy permission delegation on the XRP Ledger. An earlier version was stopped before mainnet activation after a vulnerability disclosure identified a way unauthorized transactions could charge fees to another account.
Current validator support is above 80%, which starts the process but does not by itself activate the amendment.
Under the XRPL amendment documentation, an amendment needs more than 80% validator support for two consecutive weeks. That support must hold for the full 14-day countdown; a drop below the threshold means the amendment does not meet the activation condition.
October 5 is a projected activation date, not a fixed deployment date.
Permission delegation would let an XRPL account give another account narrowly defined authority to submit particular transactions without sharing its signing keys. The delegating account would retain its own signing credentials, while the specified permissions could provide role-based controls that separate payment operations from compliance-related duties, according to RippleX’s open-source documentation.
The amendment’s mainnet availability depends on validator support remaining above the required threshold throughout the activation countdown.
PermissionDelegationV1_1 replaces the original PermissionDelegation amendment after a security issue emerged during testing. The vulnerability was reported on September 15, 2025, while the feature was being tested on devnet.
The issue could have allowed unauthorized transactions to charge fees to a different account. Following the disclosure, validators were advised to reject the original amendment, and it was disabled before it could activate on mainnet, the XRP Ledger Foundation’s vulnerability disclosure report said.
V1_1 is intended to correct that flaw, and its activation bid is a revised proposal entering the network’s formal amendment process—not the delayed completion of the original version.
The earlier halt also explains why sustained validator support is particularly consequential in this case. The process gives validators a full two-week period to support the replacement amendment before its rules would become active on mainnet.
Twenty-nine of 35 trusted validators supported PermissionDelegationV1_1 when its countdown started. That backing placed the amendment above the required level, but the mechanism requires continuous supermajority support rather than a one-time vote.
The upgrade is expected to activate on October 5 if support remains above 80% for the full period. Otherwise, the activation condition will not be satisfied, and the projected date will pass without the amendment taking effect.
For now, the central development is that XRPL has moved its corrected delegation feature into the activation window. The outcome will determine whether accounts can begin using the proposed model of narrowly delegated transaction authority without sharing signing keys.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
