{"id":13594,"date":"2026-09-23T04:39:57","date_gmt":"2026-09-23T04:39:57","guid":{"rendered":"https:\/\/cryptonews.uk.com\/?p=13594"},"modified":"2026-09-23T04:39:57","modified_gmt":"2026-09-23T04:39:57","slug":"xrpl-fixes-critical-pre-mainnet-flaw-but-client-apps-remain-at-risk","status":"publish","type":"post","link":"https:\/\/cryptonews.uk.com\/?p=13594","title":{"rendered":"XRPL fixes critical pre-mainnet flaw, but client apps remain at risk"},"content":{"rendered":"

<\/p>\n

\n

XRP Ledger (XRPL) validators have put BatchV1_1 on a conditional path to activate at 14:06:41 UTC on Sept. 29, turning a security near-miss into a live test of the network’s amendment process and its surrounding software.<\/p>\n

On Sept. 22, xrpldashboard showed 30 of 35 trusted validators supporting the amendment, above its displayed 28-vote threshold. The majority first appeared on-ledger on Sept. 15.<\/p>\n

Under XRPL’s amendment rules, support must remain above 80% for two weeks. A fall to 80% or less ends the majority period, so the activation date remains conditional.<\/p>\n

Sept. 29 is the first production test of whether XRPL’s validator process, reference implementation, and client ecosystem converted a dangerous pre-mainnet flaw into usable atomic transaction infrastructure.<\/p>\n

The validator firewall worked before mainnet<\/h2>\n

The original Batch amendment never activated on the XRP Ledger mainnet. In February, researchers found a critical authorization flaw while the amendment was still in its voting phase, and validators were advised to vote it down.<\/p>\n

XRPL Labs’ official vulnerability disclosure states that no funds were at risk.<\/p>\n

The flaw sat in the loop that checked the accounts authorizing a batch. If the code encountered a signer for a newly created account whose key matched that account, it returned success immediately instead of continuing through the remaining signers.<\/p>\n

An attacker could place that valid signer first, then add a forged entry purporting to authorize a victim account. If the amendment had gone live, the unchecked victim transaction could have executed without the victim’s keys.<\/p>\n

XRPL’s response came in two stages. Version 3.1.1 marked the original Batch and fixBatchInnerSigs amendments unsupported, blocking their activation. BatchV1_1 later replaced them with a rewritten authorization path and additional defenses.<\/p>\n

The episode was a failure caught at the boundary between software release and protocol activation.<\/p>\n

The XRPL Foundation’s final XLS-56 specification now requires a multi-account batch to contain the exact, complete set of BatchSigners whose authorization the inner transactions would ordinarily need, apart from the account whose normal signature authorizes the outer transaction.<\/p>\n

Missing, extra, duplicate, or incorrectly ordered entries cause rejection.<\/p>\n

Each BatchSigner also signs more than a loose collection of inner transactions. The payload binds the signature to the outer account, its sequence number or ticket, the selected batch mode, the ordered hashes of every inner transaction, and the BatchSigner account.<\/p>\n

A multi-signed entry also binds each nested signer account. That prevents a valid signature from being lifted into a different outer transaction or reassigned to another participant.<\/p>\n

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.<\/p>\n

Together, those changes address both the disclosed premature-success bug and adjacent ways that malformed or replayed batch data could cross authorization boundaries.<\/p>\n

A Batch contains two to eight inner transactions. Each inner transaction carries no signature or fee and is marked so it cannot be submitted independently. The outer Batch selects exactly one of four modes:<\/p>\n