XRPL validators have placed BatchV1_1 on a conditional path to activate on September 29 at 14:06 UTC, provided support remains above 80 % for two weeks. The fix addresses a critical authorization flaw discovered in February in the batch validation mechanism, where an attacker could potentially execute an unauthorized transaction from a victim account. The new protocol introduces four execution modes for multi-transaction batches and strengthens the cryptographic binding of signatures to their parent transaction, outer account, and sequence number. Nodes running versions prior to xrpld 3.3.0 or xrpl.js prior to 5.1.0 risk being blocked after activation. An outer batch can return success while inner transactions fail, requiring client applications to individually verify the result of each inner transaction.
Source: Read the original article
