By Follow-up
The XRP Ledger’s Permission Delegation upgrade did not activate on October 5 as several earlier reports had projected, after its two-week validator approval clock was reset in late September.
The amendment, PermissionDelegationV1_1, remains disabled. A fresh validator roll call at 17:16 UTC on October 5 showed support from 29 of the XRP Ledger’s 35 trusted validators, enough to keep its latest approval window running but not enough to preserve the original October 5 timetable after the earlier interruption.
If that support remains above the network’s required threshold without another break, PermissionDelegationV1_1 can now activate at approximately 21:25 UTC on October 8.
It is followed less than 18 hours later by two Batch-related amendments. The fixBatchV1_2 amendment is currently tracking toward approximately 14:13 UTC on October 9, while BatchV1_1 could follow at about 14:46 UTC.
That would put three separate XRP Ledger protocol changes into a roughly 17-hour activation window.
Why the October 5 XRP Ledger Upgrade Did Not Happen
The original October 5 projection was not invented. PermissionDelegationV1_1 had reached sufficient validator backing on September 21, with 29 validators supporting the proposal, starting what appeared to be its final two-week countdown.
Several crypto publications subsequently presented October 5 as the likely activation date.
But XRP Ledger amendments do not activate simply because they once cross the voting threshold. They must retain support from more than 80% of trusted validators continuously for two weeks.
If support falls back to 80% or below, the accumulated time is erased. A new two-week period begins only after the amendment regains the required majority.
That happened to PermissionDelegationV1_1 in late September. Its majority was re-established on September 24 at approximately 21:25 UTC, shifting the earliest possible activation from October 5 to October 8 at roughly the same time.
The situation mirrors the voting reset already affecting another major XRP Ledger upgrade. FinanceFeeds reported on September 28 that XRP Ledger’s Batch upgrade had slipped from September 29 to October 9 after validator support temporarily fell below the required threshold.
Permission Delegation Lets Accounts Hand Out Specific Powers, Not Their Keys
PermissionDelegationV1_1 changes how authority can be divided between accounts on the XRP Ledger.
An account owner can give another account permission to carry out specific actions without transferring the private keys that provide unrestricted control over the original account. A business could, for example, allow one operational account to perform defined payment functions while keeping broader control elsewhere.
The V1_1 designation matters because this is not the first version of the feature.
An earlier Permission Delegation amendment was withdrawn after developers identified a flaw before activation. The corrected implementation was subsequently introduced as PermissionDelegationV1_1.
FinanceFeeds previously examined the amendment as part of the wider xrpld 3.3.0 package when six XRP Ledger amendments reached the end of their initial validator voting window in August. At that stage, passing the initial voting period still did not guarantee activation because each amendment needed to establish and maintain its own continuous supermajority.
BatchV1_1 and Its Fix Are Now Arriving Within Minutes of Each Other
The more unusual part of the current timetable is how closely the three potential activations are now grouped.
At the October 5 live validator read, BatchV1_1 had support from 30 of 35 trusted validators. It has maintained its latest majority since approximately 14:46 UTC on September 25, putting its earliest activation at around 14:46 UTC on October 9.
BatchV1_1 allows an account to bundle as many as eight transactions into one Batch transaction. Depending on the execution mode, applications can require all of the component transactions to succeed together or use other execution rules.
That creates the infrastructure for workflows such as delivery-versus-payment, where a payment and transfer of a tokenized asset can be made conditional on each other rather than settling independently.
The accompanying fixBatchV1_2 amendment had even broader support in the latest read, with all 35 trusted validators voting in favor.
It was introduced with the emergency xrpld 3.4.1 release on September 25 after developers identified a security-sensitive issue involving the Batch implementation. The fix rejects Batch inner transactions using an incorrect transaction wrapper.
Its latest majority began shortly before BatchV1_1’s, putting its projected activation at approximately 14:13 UTC on October 9, roughly half an hour before BatchV1_1.
October 8 and 9 Are Windows, Not Guaranteed Launch Dates
The current sequence therefore looks unusually compressed: PermissionDelegationV1_1 at approximately 21:25 UTC on October 8, fixBatchV1_2 at around 14:13 UTC on October 9 and BatchV1_1 roughly 33 minutes later.
None of those timestamps should be treated as a guaranteed launch time.
PermissionDelegationV1_1 currently sits exactly at the minimum level needed to maintain its majority under the current validator set, with 29 of 35 votes. A sufficient change in validator support before October 8 would restart its countdown again.
The same rule applies to the two Batch amendments. Their stronger current voting margins provide more room for individual validators to change their positions, but activation still depends on the required supermajority remaining intact through the full two-week period.
That is the correction to the October 5 narrative. Permission Delegation has not gone live. Instead, the XRP Ledger now has three pending amendments potentially activating between the evening of October 8 and the afternoon of October 9, provided validator consensus holds this time.