Restore Block.io multisig wallet in Electrum
Restore Block.io multisig wallet in Electrum
Loading saved threads...
toXel · External communityPost link
External question — Bitcoin Stack Exchange
Author: toXel
Original post: https://bitcoin.stackexchange.com/questions/64493
License: CC BY-SA 3.0 — https://creativecommons.org/licenses/by-sa/3.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
I've exported my private keys from Block.io. They're compressed WIF keys (starting with L...).
Additionally I've got the following data from Block.io:
Address type: P2SH (obviously)
Redeem script
Redeem script hex
Two public keys
I've tried to restore that wallet in Electrum with the information I have. But as far as I understand, Electrum needs extended private keys to restore the wallet, right?
So, is there a way to restore that wallet? Maybe in a different wallet client? I've researched a whole evening but couldn't find the answer.
Quote
Report
Korben · External communityPost link
External answer — Bitcoin Stack Exchange
Author: Korben
Original post: https://bitcoin.stackexchange.com/a/68037
License: CC BY-SA 3.0 — https://creativecommons.org/licenses/by-sa/3.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
I knew that but I hadn't enough reputation to comment.
I have found a solution. I've got my BCH today from block.io which was already empty but it had a BTC on the day of fork.
So what you have to do is:
First of all you should get from security settings of you block.io profile: "Redeem Script Hex", and two private keys. (actually you will have some more strings and values but only these three required to claim your BCH).
After that:
Go to
http://www.motelmaya.com/BCH/BCH.html
I know this seems strange and may cause doubts and believe me I wasn't sure too. But the real deal was: getting BCH (I had 0,5 of BTC at block.io wallet) or getting nothing.
So, then:
Click +TX
Enter the redeem HEX that you received from block.io in the first box (Address, WIF key or Redeem Script)
Click on "Advanced options" -> "Network" -> Settings and change the network to "Bitcoin Cash (mainnet)"
Click New -> Transaction or +TX once more.
Put in the amount you want to transfer and the address you are sending to (your new BCH wallet I guess - I've used my blockchain.info wallet address), make sure that the fee is not too high (I've entered something like 0.000317
Click "Submit", you will get a long HEX string. copy it
Click "Sign", paste the copied string, paste the first private key from the block.io to the "Private key" field, click "Submit", copy the string.
Paste the string into the second box (below the "Private key" field), paste the second private key from the block.io, click Submit, copy the output
Go to "Broadcast", paste the string and click "Submit".
That's it. You will recieve TXid which you will be able to check at
https://bitcoincash.blockexplorer.com
Actually all regards should go to
ohad serfaty
but I can't comment the post where he advised this method because of low reputation.
Good luck!
Quote
Report
user190472 · External communityPost link
External answer — Bitcoin Stack Exchange
Author: user190472
Original post: https://bitcoin.stackexchange.com/a/130986
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
You don't necessarily need to restore this as a normal Electrum multisig wallet.
Electrum's multisig wallet restoration is mainly designed around deterministic wallets using seeds or BIP32 extended keys. If what Block.io exported is a set of individual WIF private keys plus the P2SH redeem script, those WIF keys are not equivalent to an xprv that Electrum can use to recreate a deterministic multisig wallet.
However, that does not mean the coins are unrecoverable.
For a P2SH multisig output, the important pieces are:
the redeem script,
the UTXO(s) paying to the corresponding P2SH address,
and enough private keys to satisfy the signature threshold encoded in that redeem script.
If the redeem script is, for example, a 2-of-3 multisig and you control two of the corresponding private keys, you can construct a transaction spending the UTXO, sign it with those keys, include the redeem script in the spending transaction, and broadcast the fully signed transaction.
In other words, this is better thought of as sweeping the P2SH output, rather than restoring it as an Electrum HD wallet.
Block.io also published an open-source multisig sweep utility for its older dTrust addresses which accepted WIF private keys and a redeem script directly. That is a good indication that extended private keys are not inherently required to spend this type of output.
I would not enter those private keys into an online recovery website. If the keys still control funds, construct/sign the recovery transaction locally or offline using audited open-source software, then broadcast only the signed transaction.
Before doing anything, verify that the public keys derived from your WIF keys actually appear in the redeem script and that you possess at least the number of keys required by its m-of-n threshold.
Quote
Report
Post Reply
Quoted from Forex.com.bd-Editorial External answer — Bitcoin Stack Exchange Author: user190472 Source score (net votes, not local likes): 0 Original post: https://bitcoin.stackexchange.com/a/130986 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. You don't necessarily need to restore this as a normal Electrum multisig wallet. Electrum's multisig wallet restoration is mainly designed around deterministic wallets using seeds or BIP32 extended keys. If what Block.io exported is a set of individual WIF private keys plus the P2SH redeem script, those WIF keys are not equivalent to an xprv that Electrum can use to recreate a deterministic multisig wallet. However, that does not mean the coins are unrecoverable. For a P2SH multisig output, the important pieces are: the redeem script, the UTXO(s) paying to the corresponding P2SH address, and enough private keys to satisfy the signature threshold encoded in that redeem script. If the redeem script is, for example, a 2-of-3 multisig and you control two of the corresponding private keys, you can construct a transaction spending the UTXO, sign it with those keys, include the redeem script in the spending transaction, and broadcast the fully signed transaction. In other words, this is better thought of as sweeping the P2SH output, rather than restoring it as an Electrum HD wallet. Block.io also published an open-source multisig sweep utility for its older dTrust addresses which accepted WIF private keys and a redeem script directly. That is a good indication that extended private keys are not inherently required to spend this type of output. I would not enter those private keys into an online recovery website. If the keys still control funds, construct/sign the recovery transaction locally or offline using audited open-source software, then broadcast only the signed transaction. Before doing anything, verify that the public keys derived from your WIF keys actually appear in the redeem script and that you possess at least the number of keys required by its m-of-n threshold.
Checking account access…