Multisig (2 of 3) BCH, one signed before fork, one after

0

Right before the BCH fork a multisig (2 of 3) transaction was signed by the other party, and mine after the fork and successfully broadcasted (coinb.in), so got my BTC.

Later I realized there might be BCH in there as well, but broadcasting the same final raw hex on the Bitcoin Cash mainnet (viabtc.com) keeps failing.

Am I missing something here? Or is it impossible because the other party's raw transaction hex code is not recognized on the BCH chain?

Broadcasting on blockdozer returns; An error occured: 16: mandatory-script-verify-flag-failed (Signature must use SIGHASH_FORKID). Code:-26

jack

Posted 2018-01-25T20:36:11.203

Reputation: 1

Was the multisig transaction confirmed before or after the fork block? If before, you should simply be able to spend it on the BCH chain. If after, both parties will have to re-sign with BCH rules, as in the answer below. It would help if you can share the txid. – Nate Eldredge – 2018-01-26T00:32:34.233

Answers

2

You cannot simply rebroadcast a bitcoin transaction on the bcash chain, due to replay protection. You need to sign the transaction using the SIGHASH_FORKID as the error message says, which means you will need to use a BCH wallet to resign the transaction

MeshCollider

Posted 2018-01-25T20:36:11.203

Reputation: 8 735

Asked: 2018-01-25T20:36:11.203

Viewed: 199 times

Active: 2018-01-25T21:38:10.750