Show Posts
Leo's guess was right, now that you have posted the transaction it lacks the other signature.
Details: Your transaction is spending a P2SH output with a 2 of 3 multi-sig redeem script. While spending it the signature script only provides a single signature so when the script is being evaluated the evaluator knows that for a OP_CheckMultiSig with with m=2 and n=3 it needs 3 pubkeys, 2 signatures and a dummy item (OP_0) and when checking the stack it sees 1 item is missing hence the invalid message based on stack size.
To solve this you simply have to sign the transaction with one of the other 2 private keys (assuming your existing signature is valid, I didn't check).
Details: Your transaction is spending a P2SH output with a 2 of 3 multi-sig redeem script. While spending it the signature script only provides a single signature so when the script is being evaluated the evaluator knows that for a OP_CheckMultiSig with with m=2 and n=3 it needs 3 pubkeys, 2 signatures and a dummy item (OP_0) and when checking the stack it sees 1 item is missing hence the invalid message based on stack size.
To solve this you simply have to sign the transaction with one of the other 2 private keys (assuming your existing signature is valid, I didn't check).
Leo's guess was right, now that you have posted the transaction it lacks the other signature.
Details: Your transaction is spending a P2SH output with a 2 of 3 multi-sig redeem script. While spending it the signature script only provides a single signature so when the script is being evaluated the evaluator knows that for a OP_CheckMultiSig with with m=2 and n=3 it needs 3 pubkeys, 2 signatures and a dummy item (OP_0) and when checking the stack it sees 1 item is missing hence the invalid message based on stack size.
To solve this you simply have to sign the transaction with one of the other 2 private keys (assuming your existing signature is valid, I didn't check).
Details: Your transaction is spending a P2SH output with a 2 of 3 multi-sig redeem script. While spending it the signature script only provides a single signature so when the script is being evaluated the evaluator knows that for a OP_CheckMultiSig with with m=2 and n=3 it needs 3 pubkeys, 2 signatures and a dummy item (OP_0) and when checking the stack it sees 1 item is missing hence the invalid message based on stack size.
To solve this you simply have to sign the transaction with one of the other 2 private keys (assuming your existing signature is valid, I didn't check).
Hi & thanks one more!
You wrote, i need one of the other 2 private keys. How can i get this? isn't that the case that everyone has a private key and that it is confidential?
