You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I want broad the hex ,"0100000001ecef8c2f2b0da5e47c9934935b9b2ae5d5742164b3a7258ce8c460e73da4b59400000000055657935d87ffffffff012c010000000000001976a914b163d850125f1b65eadbcf15f88b7ef16836c1ee88ac00000000" I got error mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element)
I can make sure my txid and vout is right. How can I solve this problem , thank you
The text was updated successfully, but these errors were encountered:
please ask general questions about bitcoin script on the stack exchange, this is not specifically related to this repository, and make sure to use markdown code blocks to make code readable in your post (i edited it for now)
i did spot the error in your code:
p2sh needs the script on the stack top, not the loose opcodes (see https://github.com/antonilol/btc_stuff/blob/master/p2sh.js#L20-L24, the last list element is the compiled redeemScript)
changing a few numbers in your raw transaction makes it valid as i thought (tested with the testmempoolaccept rpc) 0100000001ecef8c2f2b0da5e47c9934935b9b2ae5d5742164b3a7258ce8c460e73da4b5940000000006565703935d87ffffffff012c010000000000001976a914b163d850125f1b65eadbcf15f88b7ef16836c1ee88ac00000000
I had to send utxo from p2pkh to p2sh address, here is my code .
and then I want unlocking this utxo from p2sh tp p2pkh, here is my code
When I want broad the hex ,"0100000001ecef8c2f2b0da5e47c9934935b9b2ae5d5742164b3a7258ce8c460e73da4b59400000000055657935d87ffffffff012c010000000000001976a914b163d850125f1b65eadbcf15f88b7ef16836c1ee88ac00000000" I got error mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element)
I can make sure my txid and vout is right. How can I solve this problem , thank you
The text was updated successfully, but these errors were encountered: