Mayukha Vadari 0dfaf80a27 fix: Give a multi-signed BatchSigner its own signing prefix ...

A batch signer signs one of two payloads: the batch data plus its own
account, or, when it signs from a signer list, the batch data plus its
own account plus the signer's account. Both used the BCH prefix, so the
two payloads shared a hash space, unlike TxSign and TxMultiSign, which
are split for exactly this reason.

The multi-signing form now uses a BCM prefix. The two payloads already
differed in length, so this closes no attack; it applies the convention
that every distinct signing payload gets its own prefix.

Batch is gated on featureBatchV1_1, which is not enabled on any network,
so no existing signature changes and no amendment gate is needed.

2026-09-02 15:20:31 -04:00

..

xrpl

fix: Give a multi-signed BatchSigner its own signing prefix

2026-09-02 15:20:31 -04:00