Debugger is giving a bad sig error for a valid signature. I know it's valid because th

Script verification fails for valid transaction about btcdeb HOT 3 CLOSED

bitcoin-core commented on May 26, 2024

Script verification fails for valid transaction

from btcdeb.

Comments (3)

prestwich commented on May 26, 2024 1

works for me after recompiling thanks! 👍

from btcdeb.

prestwich commented on May 26, 2024

Setting the DEBUG_SIGHASH gives the following additional output:

#004 01000000
#032 82f92de3ee96290265eea85e2ad5c91d4ae05594351ca1d93ea7db8b0c80f9ca
#032 c992651ac89a97aecd0811c1761915a8e2c8f5153d1bdd994a789e6bd86ab717
#032 230666759103969e1df0906f7dd421d83caf2d13f0fb49f11f15435e82caa7bd
#004 01000000
#001 19
#025 76a914ef664686809ac47fdb5a1909bde542f248cf200b88ac
#008 0000000000000000
#004 feffffff
#032 4a647f7c1e328f7e8c3c3b648ead0c819f5c70bac32f318aa13f8c9381d071ef
#004 00000000
#004 01000000
error: Signature must be zero for failed CHECK(MULTI)SIG operation (is this a historical transaction from before NULLFAIL enforcement? Try with --modify-flags=-NULLFAIL)

I checked this against my bip143 implementation. It looks like the prevout value is not being set properly (the #008 0000000000000000). Other than that, everything is fine. This may be some problem with the --txin=... logic? (or I may be misunderstanding it? it seems to work properly for other txns)

from btcdeb.

kallewoof commented on May 26, 2024

You are absolutely right; the value was somehow hard-coded to use the 0th input, it looks like. Will push a fix in a bit, once I know that's actually the issue.

from btcdeb.

Recommend Projects