New answers tagged multi-signature
1
The "01" byte at the end is the sighash type byte (specifically, 01 means SIGHASH_ALL, indicating that all inputs and outputs are signed). Such a byte is required for all signatures in Bitcoin scripts (both in legacy and segwit signatures). However, that byte is part of the DER-encoded signature; it's appended to it.
Presumably your hardware wallet ...
0
If solution suggested in the comment resolved your problem it's related to address_type in both RPC commands. It is legacy by default for createmultisig and set by -addresstype in bitcoin.conf for addmultisigaddress
You have used public keys in first command and addresses in second so I am not sure if the addresses are for same keys and in the same order.
...
0
2MtLR5mKgWRZBYtCYiSuaKpTUSuney9Cg2V is your new address which is derived from scriptHash 0x0bf37781383277cbb4e544c402f5265a51f4d8289. Go all the way back to step 2 and send 0.005 & 0.004 to 2MtLR5mKgWRZBYtCYiSuaKpTUSuney9Cg2V. scriptPubKey of those transactions will be both OP_HASH160 0bf37781383277cbb4e544c402f5265a51f4d828 OP_EQUAL.
Retrieve those ...
1
Your redeem script hash should be:
RIPEMD160(SHA256(0x522103e33af80b92e4efd64852166d6126e10aafdcc741579c67c6aa9eb89080cebeb22102df4bf6a54f79b333b7796d2941de13b1755c00c09f4dbf696c7729aea29462102102c099a12b6cba679ad56d8e793847f422634bc84b42cb3fae0b00a6943f56921253ae))
= 0bf37781383277cbb4e544c402f5265a51f4d828
Which results this address:
...
Top 50 recent answers are included
