XRPL Validators Set Conditional Activation Date for Repaired Batch Amendment

XRPL validators have put BatchV1_1 on a conditional path to activate at 14:06:41 UTC on Sept. 29, marking a live test of the network's amendment process and its surrounding software.

The original Batch amendment never activated on the XRP Ledger mainnet due to a critical authorization flaw discovered in February, which could have allowed an attacker to execute unchecked transactions without the victim's keys.

XRPL Labs' official vulnerability disclosure states that no funds were at risk. The flaw was fixed in two stages: version 3.1.1 marked the original Batch and fixBatchInnerSigs amendments unsupported, blocking their activation, and BatchV1_1 replaced them with a rewritten authorization path and additional defenses.

The XRPL Foundation's final XLS-56 specification now requires a multi-account batch to contain the exact set of BatchSigners whose authorization the inner transactions would ordinarily need, apart from the account whose normal signature authorizes the outer transaction. Each BatchSigner signs more than just a collection of inner transactions.

The merged reference implementation adds enforcement around that design, including signer ordering and uniqueness checks, transaction-count bounds, rejection of directly submitted inner transactions, and protections for ledger replay. Activation will show whether XRPL's validator process can stop a dangerous amendment and route operators to a disabled release.