Topic: Raw transaction to bech32 multisig (Read 177 times)
Thanks, I did 'decoderawtransaction' and it seemed fine, although on a technical level my comprehension is limited. That's part of my hesitation, I guess.
The most common thing that could go wrong is that you did not make a change output. If you do not make a change output that sends the change to another address that you control, you could end up sending all of your change to fees instead.
Otherwise, everything else should be fine. You can double check that your transaction is correct by using decoderawtransaction.
Otherwise, everything else should be fine. You can double check that your transaction is correct by using decoderawtransaction.
Hi, as stated, I tested making a raw transaction from a tx-id associated with a legacy address to an electrum generated multisig, I haven't signed the raw transaction, but the latest Bitcoin Core client understood the raw transaction input and gave me a numerical string which I could sign.
For some reason, I'm still a bit worried that I could make a gigantic blunder in one way or another. My point is, I've made sure I have access to the multisig keys, what could go wrong when making raw transactions this way?
Thanks.
For some reason, I'm still a bit worried that I could make a gigantic blunder in one way or another. My point is, I've made sure I have access to the multisig keys, what could go wrong when making raw transactions this way?
Thanks.
Jump to: