The XRP Ledger is approaching one of its busiest upgrade windows of 2026, with three amendments potentially activating within less than 18 hours of each other on Oct. 8 and Oct. 9.
The current activation schedule puts PermissionDelegationV1_1 first at approximately 21:25 UTC on Oct. 8, followed by fixBatchV1_2 around 14:12 UTC and BatchV1_1 around 14:46 UTC on Oct. 9, provided validator support remains above the required threshold.
The changes affect very different parts of XRPL. The official XRPL amendment documentation describes PermissionDelegationV1_1 as granular account authorization, while BatchV1_1 introduces atomic groups of transactions that can be processed together.
Oct. 8 Could Bring Bank-Style Account Controls
PermissionDelegationV1_1 would allow an XRPL account to give another account specific powers without handing over its master keys.
That could let an institution separate compliance, payments and operational responsibilities across multiple accounts. The structure is particularly relevant for banks, stablecoin issuers and other organizations where one wallet should not control every function.
The feature is already approaching its revised activation date after an earlier dip in validator support reset its countdown. Its institutional account-control model could now become available on Oct. 8 if majority support holds.
Oct. 9 Could Bring Batch, and Its Security Fix
The second day is centered on Batch transactions.
BatchV1_1 lets users combine up to eight transactions into a single operation, enabling structures where multiple steps can succeed together or fail together. That functionality has attracted interest for settlement, atomic swaps and more complex institutional transactions.
Its activation was originally expected in September before validator support dropped below the required level, pushing the BatchV1_1 countdown to Oct. 9.
But BatchV1_1 will arrive alongside an additional safeguard. XRPL developers released xrpld 3.4.1 as an emergency security update, introducing fixBatchV1_2 after identifying security-sensitive protocol issues. Servers that remain outdated when the amendment activates risk becoming amendment blocked.
That emergency security release makes Oct. 9 more consequential than a normal feature launch.