XRP Ledger’s Permission Delegation Did Not Go Live on…
By Abdelaziz Fathi
AI summary of the source article
The XRP Ledger amendment PermissionDelegationV1_1 did not activate on October 5 because its continuous two-week validator approval clock was reset in late September when support dropped below the required 80% threshold. After regaining sufficient votes on September 24, the earliest activation moved to approximately October 8 at 21:25 UTC. As of October 5, 29 of 35 trusted validators supported the amendment, meeting the exact minimum requirement. If support holds, PermissionDelegationV1_1 will activate alongside two other upgrades on October 9: fixBatchV1_2 and BatchV1_1, compressing three protocol changes into a roughly 17-hour window.
Why it matters
The upgrade allows account owners to delegate specific actions without handing over private keys, facilitating corporate operational controls and workflows like delivery-versus-payment when combined with the upcoming Batch amendments.
Key facts
- PermissionDelegationV1_1 requires continuous support from over 80% of trusted validators for two weeks and had 29 of 35 votes on October 5.
- A voting reset shifted the earliest activation from October 5 to approximately 21:25 UTC on October 8.
- Two Batch-related amendments, fixBatchV1_2 and BatchV1_1, are projected to activate on October 9.