XRP Ledger began a 14-day activation countdown on Sept. 21 for PermissionDelegationV1_1, an upgrade that would let one account authorize another to make payments or approve customers on its behalf. Backed by 29 of 35 trusted validators—above the required 80%—the change could activate on Oct. 5 at 11:18 UTC if support persists.
The amendment enables accounts to divide authority by job function, allowing, for example, an internet-connected compliance system to approve customer accounts while the keys with full control remain offline. At least 28 validators must continue signaling support throughout the window; any dip below that level resets the clock.
What does the XRP Ledger upgrade change?
PermissionDelegationV1_1 would allow an account to delegate specific actions—such as initiating payments or approving customers—to another account without sharing full-control keys. That separation lets operators keep master keys offline while assigning narrowly scoped duties to connected systems, including compliance workflows for token issuers or other regulated operations.
The design aims to formalize role-based access within the XRP Ledger’s transaction model. Instead of a single set of credentials unlocking every permission, accounts can assign discrete capabilities so payment initiation or customer onboarding can proceed under tight constraints. A stablecoin issuer, for instance, could let a live compliance engine approve eligible holders while safeguarding broader controls in cold storage.
By decoupling operational functions from custody of master keys, the feature targets attack-surface reduction and operational resilience. It aligns with institutions’ preference for least-privilege architectures where automation handles narrow tasks, and human-controlled keys retain ultimate authority.
Milestone | Requirement | Specific number/date |
|---|
Countdown start | Activation window begins | Sept. 21 |
Support threshold | Minimum backing needed | ≥80% |
Initial support | Validators in favor | 29 of 35 |
Minimum validators | Ongoing support needed | 28 validators |
Potential activation | Go-live if support holds | Oct. 5 at 11:18 UTC |
Reset condition | Clock restarts | Support falls below 28 |
When could PermissionDelegationV1_1 go live?
The upgrade could activate on Oct. 5 at 11:18 UTC if validator support remains at or above the 80% threshold for the entire 14-day window. Should backing drop below 28 validators at any point, the activation clock resets and a new 14-day period begins once sufficient support returns.
The current tally—29 of 35 trusted validators—exceeds the threshold, offering a margin for fluctuation but not a guarantee. The amendment requires sustained consensus, not just a momentary supermajority. Network participants will monitor the live signaling posture across the window to confirm continuity through the precise activation timestamp.
Operationally, a clean activation at the scheduled time hinges on maintaining at least 28 validator approvals with no interruptions. Any interruption restarts the process, extending the timeline and delaying production use of delegated permissions for payments and compliance approvals.
Why does splitting payment and compliance duties matter?
Delegation allows institutions to separate payment initiation from compliance decisions while protecting full-control keys offline. That approach supports least-privilege operations, enabling internet-connected services to approve customers or trigger defined transactions without exposing broader account authority to online risk.
For token issuers and other operators that must verify customer eligibility, automated approval systems can be scoped to that single purpose. Meanwhile, treasury and governance controls stay secured behind offline keys. The result is a tighter security posture paired with practical automation for regulated workflows.
This division of duties is intended to reduce operational friction and the blast radius of key compromise. If a delegated key is exposed, its permissions are limited by design, helping contain incidents and simplifying recovery.
What should validators and issuers watch next?
Participants should track validator signaling through Oct. 5 at 11:18 UTC and confirm support stays at or above 28 validators. Issuers and operators evaluating the feature can prepare role definitions and access boundaries so that, if activated, delegated functions are narrowly scoped from day one.
Beyond the activation checkpoint, the focus will shift to real-world configuration: defining which actions are delegated, instituting monitoring, and setting revocation procedures. A clear rollback path remains critical, especially where internet-exposed systems handle approvals or initiate payments on behalf of primary accounts.
If the clock resets due to insufficient support, timelines extend and testing cycles should continue in parallel. The amendment’s effectiveness ultimately depends on precise permissioning and operational discipline once live.
Activation, if achieved, would mark a step toward institution-friendly controls on the XRP Ledger by embedding delegated authority for payments and compliance into the base protocol.
XRPL XLS-75: Permission Delegation
PermissionDelegationV1_1 in rippled
XRPL Transaction Queue Documentation
