XRPL Batch Wrapper Bug: A Consensus and Indexer Failure Prevented

XRPLs October 9 security report describes a second, independent flaw in the Batch transaction feature. Unlike the payment-engine overflow, this bug threatened ledger availability and data compatibility, not the supply of XRP. A crafted inner-transaction wrapper could have been interpreted differently by servers on different versions. The developers say Batch had not been activated on Mainnet when the bug was found, and no funds were lost and no consensus failure occurred.Why a field name could split a network　　Batch allows a group of signed transactions to be submitted together. Each inner transaction is supposed to be carried inside a field called RawTransaction. The faulty validation logic accepted other object-type wrapper fields if that field had no restrictive template.　　Older xrpld 3.3.0 and newer 3.4.0 defined different object fields. A deliberately nonstandard Batch payload could be accepted and relayed by one version but fail deserialization in another. If enough validators ran the incompatible combinations, the trusted validator group could disagree on the contents of a ledger and potentially stop validating new ledgers.　　The technical issue is distinct from private-key theft. Every inner transaction still required ordinary valid signatures and balance checks. The attacker could not simply authorize another users payment without that users signature.