XRPL Fixes Critical Pre-Mainnet Flaw, Client App Risks Remain

The XRP Ledger (XRPL) has fixed a critical pre-mainnet flaw in its BatchV1_1 amendment, but the fix may not be enough to prevent issues with client applications.

The original Batch amendment was rejected by validators on February 22 after researchers discovered an authorization flaw that could have allowed attackers to execute transactions without victims' keys. The issue was fixed in two stages: first by marking the original Batch and fixBatchInnerSigs amendments as unsupported, and then by replacing them with a rewritten authorization path in BatchV1_1.

The new amendment requires a multi-account batch to contain the exact set of signers whose authorization is needed for each inner transaction. The payload also binds each nested signer account to prevent signatures from being lifted into different transactions or reassigned to other participants.

However, the activation of BatchV1_1 on September 29 will not necessarily prove that applications have adopted the feature or that users want it. The amendment's success will depend on whether servers, signing libraries, wallets, and data infrastructure agree on the new transaction format and its results.