Topic: problem trying to spend form multi sig address (Read 267 times)

p2wpkh-p2sh is for SegWit addresses only. 

NOTE: a "3"-type address is NOT necessarily a Multi-Sig address... 3 == "P2SH"... this could be Multi-Sig, or it could be "SegWit wrapped in P2SH" (aka P2WPKH-P2SH).


Given you were using the Multi-Sig functionality on coinb.in, it is more likely that the multi-sig was created from "legacy" addresses. Trying to sign multi-sig transactions in Electrum using individual private keys is not easy (I'm not even sure if it's actually possible). I've been trying to do this, but when I attempt to load the partially signed transaction into the wallet that contains just a single private key... I get a "Transaction unrelated to your wallet" note on the transaction... and Electrum won't sign it



I've double checked... and the Public Key for the PrivateKey/Address that is in the wallet is indeed one of the public keys used for the redeem script, so it's either some weird quirk with Electrum Testnet... or trying to sign transactions from non-seeded (or non-xprv wallets) is not supported.

I even tried to use the "signtransaction()" command on the Electrum console... and that also fails to sign the transaction (the output hex is identical to the input hex)


Honestly, I think that you might be be better off using Bitcoin Core, so you can manually use the createrawtransaction and signrawtransaction commands from the console. I think you can probably even do this without having a fully synced client... as you can simply provide the required UTXO data when creating/signing the transaction.

 I tried to import the private keys as you said but the return is 3 different multisig addresses, none with funds...

[
To explain it simply, an ECDSA signature has generally two values (R and S value). The S value shouldn't be higher in order for the signature to pass and the tx to be broadcasted in the network. There is certain threshold limit for the S value to be present. Your value might be higher than expected.
Can you provide raw transaction data, so that let me see what's going wrong with the S value!
[/quote]

I don't get it, what could I have done wrong?

the unsingned raw transaction is as following: 0100000001db86b5ec2bad812380ca83dd1881181b19f89623f6701645a2b5538618ca168e00000 00000ffffffff01aa51d900000000001976a9145af26d1c2b75ab6ed7e43d36951aedd830e95fe6 88ac00000000

You can also just import the private keys. Create a new wallet by choosing 'Import Bitcoin addresses or private keys'.
You just have to tell electrum how to handle them (clicking the 'Info' button on import screen).

Place p2wpkh-p2sh: in front of your private keys (one per line) and it should work. (e.g. p2wpkh-p2sh:KyjHQ9JdAAPkrnLvpnwx7Uvpys3HHQN6ubKSB5vnwx7UvpARjwYZ).

Is the private key in correct format? Electrum supports only private keys in wif and Mini formats! You can use the QR code to easily scan and import the keys.
Have you entered only one private key per window or just entering them continuously?

Since the coinb address starts with 3 (which is a p2sh format) you need to prepend them to p2wpkh-p2sh format for electrum to recognize them before importing the keys. Since electrum supports only bech32 and legacy address, a possible solution is to transfer the coins to the new wallet after creating one in electrum.

Though I have never used coinb website, I may even be wrong in guiding you.

To explain it simply, an ECDSA signature has generally two values (R and S value). The S value shouldn't be higher in order for the signature to pass and the tx to be broadcasted in the network. There is certain threshold limit for the S value to be present. Your value might be higher than expected.
Can you provide raw transaction data, so that let me see what's going wrong with the S value!

it seems that i can't import my private keys to electrum since it requires a master private key XPRV which i do not have, i have the standard private keys, all of the 3.

almost manege to do it with this coinb.in/multisig this time it could sign the transaction for the second time, but as i am very lucky another problem occurred... i signed it for the second time, verified it and it was saying that the transaction is signed 2 times out of 2 required, but when i try to broadcast the transaction i get i error message:" 64: non-mandatory-script-verify-flag (Non-canonical signature: S value is unnecessarily high)" what could that be?

Does the text above says: "Add cosigner 1", yes?
Electrum's multisig wallet even without cosigner service like TrustedCoin requires you to restore three (if the address requires 3 signatures) different Electrum wallets from each of the Master Public Key of the cosigner.
Then, use their xpub as the cosigner 1, 2 or 3.
The tricky part is how to restore that address, so you must use the xpubkey or seed of your coinb.in account, not just the address' private keys.
AFAIK, you can't use Electrum to do that (I'm not using coinb.in, so I might be wrong).

These links may help:

• How to Create and Use a Multi-Sig Bitcoin Address (almost the same interface as coinb.in)
  
• Have you tried their multisig sublink? coinb.in/multisig or just add /multisig to your bookmarked coinb site to be sure.

i have a problem importing the private keys in electrum.

"please enter the master public key(xpub) of your cosigner" ?
enter their master private key(xprv)if you want to be able to sign for them" well in my case i will sign the whole thing so i want to import all private key but when i paste the private keys there the next button still unavailable...

yes i am sure i am using the corrects private keys, it is a 2-3 multi sig, i signed with one of the 3 private key, then i can verify the output and it says the transaction is signed but just one time, i need one more signature, so i take this same output and paste into the sign form to be signed with a second private key, but when i try to sign for the second time the output does not update.

Are you signing with the correct private key? Key in your redeem script into https://coinb.in/#verify and check if you have used the correct private key corresponding to the correct addresses. Just to confirm, you are putting the raw TX signed by the first key into the second key right?

Electrum allows you to setup a multisig wallet and you can sign it there.

havis there another client i could use to spend those fund? if so, could some one advice me on how to do this? thanksing problem with coinb.in.

i want to redeem some funds from a multisig address, so i created a new transaction from the redeem script, added the output, generated the raw transaction, picked it and paste in the sign section, signed with the first private key, then it generate a signed transaction arround 190 bytes, but when i try to sign with the second private key the result is the same as the previous, a 190 exactly same output from the first signing... am i doing anything wrong? or is there a problem with coinb.in? could someone help?