XRP Ledger Activates PermissionDelegationV1_1 After30-of-35 Validator Votes
The XRP Ledger enabled PermissionDelegationV1_1 on Oct. 8, letting accounts authorize delegates to transact without handing over their keys.
Why it matters
Permission Delegation is a step toward handing transaction rights to other accounts without exposing the account's keys, a pattern used by custodial and automated systems. The PaymentBurn caution and the stalled fixCleanup3_4_0 amendment mean the feature ships with a known carve-out rather than a clean bill of health.
Where the sources disagree
Timing of PermissionDelegationV1_1 activation
earliest activation about 21:25 UTC Oct. 8, actual activation possibly around 21:42 UTC
The Crypto Basic
activated Oct. 8 at 5:29 p.m. ET, ledger 107,524,865
Unchained
The Crypto Basic reported an earliest activation point of roughly 21:25 UTC on Oct. 8 with actual activation possibly near 21:42 UTC given flag ledgers, while Unchained reports the amendment enabled at 5:29 p.m. ET per XRPL Dashboard.
Key facts
The XRP Ledger enabled the PermissionDelegationV1_1 amendment on Oct. 8 at ledger 107,524,865.
Disputed figureReported by Unchained
The amendment allows an account to authorize other accounts to send transactions on its behalf without sharing its keys.
Reported by Unchained
The live XRPL amendment tracker showed 30 of 35 trusted validators voting yes for PermissionDelegationV1_1, against29 votes needed to keep the countdown running.
30Reported by The Crypto Basic
The current validator majority began on Sept. 24 at 21:25 UTC after an earlier approval period was interrupted.
Disputed figureReported by The Crypto Basic
XRPL amendments require more than 80% of trusted validator support for 14 consecutive days, and support at or below 80% resets the countdown.
80 %Reported by The Crypto Basic
PermissionDelegationV1_1 replaces an earlier version that was pulled after a critical bug was found.
Reported by Unchained
The XRPL amendments page recommends against delegating the PaymentBurn granular permission until fixCleanup3_4_0 is enabled, because a delegate may be able to create new trust line or multi-purpose tokens rather than only destroy existing ones.
Reported by Unchained
What happened
The XRP Ledger activated the PermissionDelegationV1_1 amendment on Oct. 8 at ledger 107,524,865, which Unchained places at 5:29 p.m. ET, citing XRPL Dashboard. The feature lets an account authorize other accounts to submit transactions on its behalf; each delegate can hold up to 10 permissions, and the granting account replaces or revokes them by submitting a new list, with any omitted permission removed. The Crypto Basic said the amendment's earliest activation point was about 21:25 UTC on Oct. 8, with 30 of 35 trusted validators voting yes in the latest roll call against a 29-vote requirement, after the majority had held since Sept. 24 at 21:25 UTC. PermissionDelegationV1_1 replaces an earlier version pulled after a critical bug, and Unchained, citing the XRPL amendments page, carries a caution that delegating the PaymentBurn granular permission should be avoided until fixCleanup3_4_0 is enabled, because a delegate may otherwise create new trust line or multi-purpose tokens rather than only destroy existing ones. That fix stood at 27 of 35 validators, two short of the 29 Unchained lists as the requirement, on Oct. 9. Unchained also reported on Oct. 8 that rippled version 3.4.1 stops counting a validator's vote under review on the project's GitHub repository. Separately, Bitcoinist reported that the BatchV1_1 amendment is still inside its own activation window and is expected to activate around Oct. 9, bundling multiple transactions into an atomic group.
How the story developed
- Update
Earlier approval period interrupted, validator majority restarts
The Crypto Basic said the current majority began Sept. 24 at 21:25 UTC after an earlier approval period was interrupted, which is why reports of an Oct. 5 activation did not happen.
- Update
rippled 3.4.1 vote-counting issue reported on GitHub
Unchained said a report filed Oct. 8 on the rippled GitHub repository says version 3.4.1 stops counting a validator's vote.
- Update
PermissionDelegationV1_1 counted at 30 of 35 validator votes
The Crypto Basic reported 30 of 35 trusted validators voting yes at the latest roll call, with 29 needed to keep the countdown running.
- First report
First report by The Crypto Basic
Permission Delegation Is Just Hours Away on XRP—What Changes for XRPL Accounts
- Official statement
PermissionDelegationV1_1 enabled at ledger 107,524,865
Unchained cited XRPL Dashboard for activation on Oct. 8 at 5:29 p.m. ET, with the amendments page cautioning against delegating PaymentBurn until fixCleanup3_4_0 is enabled.
- Independent corroboration
Independently corroborated by Bitcoinist
XRP Ledger Batch Upgrade Nears Activation After Validator Vote Reset
- Update
BatchV1_1 amendment enters activation window
Bitcoinist reported BatchV1_1 is inside the XRPL amendment process and is expected to activate around Oct. 9 if validator support stays above the required threshold.
- Update
fixCleanup3_4_0 two votes short of requirement
Unchained reported XRPL Dashboard showing fixCleanup3_4_0 at 27 of 35 trusted validators, two short of the 29 it lists as the requirement, so the fix has not reached majority.
How coverage built up
Independent sources over time, counted the way the consensus panel counts them: a republication of a wire story does not move the line.
- 8 Oct 2026, 14:57 UTC: The Crypto Basic — 1 independent source, 1 reports
- 8 Oct 2026, 22:00 UTC: Bitcoinist — 2 independent sources, 2 reports
- 9 Oct 2026, 10:27 UTC: Unchained — 3 independent sources, 3 reports
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| The Crypto Basic Crypto media | Permission Delegation Is Just Hours Away on XRP—What Changes for XRPL Accounts | Original | |
| Unchained Crypto media | XRP Ledger Enables Account Delegation as a Token-Minting Fix Lacks Two Validator Votes | Independent | |
| Bitcoinist Crypto media | XRP Ledger Batch Upgrade Nears Activation After Validator Vote Reset | Independent |