coinbin
coinbin copied to clipboard
OutCast3k
Cannot broadcast multisig redeem tx
Error Error 16: mandatory-script-verify-flag-failed (Non-canonical DER signature)
when broadcasting although transaction verifies ok.
More details :
- https://counterpartytalk.org/t/redeem-multisig-dust-cannot-broadcast-mandatory-script-verify-flag-failed/2568
- https://github.com/bitcoin/bitcoin/issues/9455
SAME EXACT PROBLEM for me and i see nobody responed since jan 4th OUCH! this sucks
Having the same problem - with the dogecoin network. Created 3 addresses, created a multisig 3-of-3, created a transaction and signed with all 3 private keys. Verify transaction says everything is okay.
Transaction in question:
01000000013f7ec7d836246ef44e6b357583d2bd372fb019a5ff7302362ba5547874c94db400000000fd440100473044022077fd856f565a89aff6977d64d3c8a15781353398f3388f5a33f923a897258abb022052dbdf43c39e1ec69bc8bcd784d9748981a6cbeec59fced0562121a148f6eb46014730440220274f02193d0702b7a1f076d0d5c042a916bf4ac36bb945f83c89185ac389e97602202bc19a3692fcd15a8fe54afa9e0cad33e5a46ae08eb7aaed19ddec6caccca464014730440220274f02193d0702b7a1f076d0d5c042a916bf4ac36bb945f83c89185ac389e97602202bc19a3692fcd15a8fe54afa9e0cad33e5a46ae08eb7aaed19ddec6caccca464014c6953210354a5d596a8122762bec90f42808dc7a9cdcf76a5e15df07d2180fd3b6adf650521032d1787a0f632f66e7e18355c07a81947d795c699dec8d13550157ec6c9d755d7210327f5d079f3fa2f63362fc2610177e34eb309a3de02562ce484611182aa20852453aeffffffff0180d1f008000000001976a9143f830c5c5f406a94f968405e3fc0cfaf2480f2b688ac00000000
Transmitting with Dogecoin client says 16: mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element) (code -26)
Website says A valid signed transaction hexadecimal string is required. Please check if all inputs in the given transactions are still available to spend. See the "Is Tx Output Spent?" API call for reference.
EDIT looks like in my case, it was a too low fee?
i have a pretty similar problem, created a raw transaction out of the reedem script(arround 85bytes), signed it with one PK(arround 190 bytes), but when i try to sign using the sencond PK the transaction that is generated is exactly the same as the previous as if it hasnt been signed, 190 bytes...
