TL;DR:
- XRP Ledger’s PermissionDelegationV1_1 entered its two-week activation window after receiving support from 29 trusted validators across the network.
- The amendment lets accounts delegate specific operational permissions without sharing signing keys, targeting compliance, institutional workflows and more granular account controls.
- Activation could occur October 5 if support stays above 80% continuously, while any drop to 80% or lower would reset the countdown and delay mainnet deployment under XRPL’s amendment governance rules.
The XRP Ledger’s PermissionDelegationV1_1 amendment has entered its two-week activation window after securing support from 29 trusted validators. XRPScan data places the earliest possible activation at 11:18 a.m. UTC on October 5, provided validator backing remains above the required threshold throughout the countdown. The vote moves XRPL closer to enabling protocol-level permission delegation, allowing accounts to assign specific operational authorities without handing over their signing keys. The amendment replaces an earlier version that was disabled after a critical bug prevented it from reaching mainnet.
Permission Delegation Moves Toward Mainnet
PermissionDelegationV1_1 follows the XLS-75 standard and is designed to let account owners grant selected permissions to other accounts while retaining control over those rights. Delegated authorities can include operational tasks relevant to compliance teams, asset issuers and other institutional workflows, while certain account-level controls remain non-transferable. The structure is intended to support separation of duties directly at the protocol level rather than forcing organizations to rely on offchain workarounds. That design makes the amendment particularly relevant for regulated issuers and other entities that need granular control over who can perform specific actions.
Activation is not guaranteed simply because 29 validators voted in favor. XRP Ledger amendments must maintain support above 80% continuously for two weeks before becoming enabled, and the countdown resets if backing falls to 80% or lower. The next milestone therefore depends on sustained validator consensus rather than the current vote count alone. The mechanism mirrors the governance process used for other XRPL upgrades, including recent amendments approaching activation through the same supermajority requirement.
The revised amendment also represents a second attempt to bring permission delegation to XRPL after the original implementation was withdrawn. The earlier version contained a critical flaw, leading developers to disable it and replace it with the hardened V1_1 release included in xrpld 3.3.0. That history raises the importance of the current activation period, because validators are effectively assessing a corrected version of a feature previously blocked before mainnet deployment. The broader release also introduced other governance items tied to XRPL functionality, reinforcing the network’s ongoing validator-driven upgrade process. If support holds through October 5, PermissionDelegationV1_1 could become another building block for institutional and operational use cases on the XRP Ledger. For institutions, that would make delegated account administration a native network capability.
