Ensuse either functional or unit tests cover CashToken-bearing inputs that are locked by p2sh multisig
This is in response to the latest BU consensus bug which was fixed here. We need to ensure our functional tests cover this test case:
- input's locking script is p2sh, redeem script is classic M-of-N multisig
- input's locking script also has token data (that is, the coin has a token)
- spend the input in a txn, sign for it, and ensure the node accepts the txn
- CAVEAT: signing the input and calculating the sighash for it should be done independently of normal BCHN signing code as part of the test, so it doesn't rely on the same codepath!
Edited by Calin Culianu