How can I import Blockchain.Com Wallet in Bitcoin Core ?

[DigitalMonk]

I have a Wallet in Blockchain.Com. I want import it to my Bitcoin Core QT. It is not allowing me to import it. Can anyone assist me and guide me step by step to import my Bitcoin Address ?

Thank you for your help.

[Charles-Tim]

Bitcoin Core does not support seed phrase.

Blockchain.com is a web wallet, how it generates seed phrase would make me to suggest you to generate a wallet on Bitcoin Core and send your coin from Blockchain.com to Bitcoin Core instead.

Bitcoin transaction fee is not high, you can even do it when the mempool is most not congested, it is around 1 to 3 sat/vbyte right now, when I was posting this.

[NeuroticFish]

I have a Wallet in Blockchain.Com. I want import it to my Bitcoin Core QT. It is not allowing me to import it. Can anyone assist me and guide me step by step to import my Bitcoin Address ?

Thank you for your help.

I also agree with Charles-Tim: it's easier and safer to just create a new wallet into Bitcoin Core and send the funds there. If you use minimum fee (1 sat/vbyte) it will most probably be processed this week-end (maybe even today).
I will add that it's not only that Bitcoin Core cannot use the seed, it's also that since it was user with a web service, I would not consider it that safe.

Plus:
* if you have big amount of funds, you may want to buy a hardware wallet for safety
* keep in mind that Bitcoin Core needs to download the whole blockchain (450 GB) and by default it also stores it (you can prune it, but that can come with other surprises like the need to re-download everything when you change wallet); this means time and resources you have to be prepared for.
* you will have to keep backup of your bitcoin core wallet.dat file
* if you think that bitcoin core is not the best option for you, maybe you take a look at SPV wallets (simple wallets) that don't need so much resources (they connect to external servers, they also use seed so the backup is easier) like Electrum or Sparrow.

[DigitalMonk]

Does its mean if the Bitcoin Core is fully downloaded and synced, the import functionalities do not work ?

I created few wallets in Bitcoin Core but I'd does not allow me to sign or verify messages. I could not even import a paper wallet and private key in Bitcoin Core. If I down load the complete blockchain will the Bitcoin Core work properly ?

Thanks for your help.

[OmegaStarScream]

Does its mean if the Bitcoin Core is fully downloaded and synced, the import functionalities do not work ?

I created few wallets in Bitcoin Core but I'd does not allow me to sign or verify messages. I could not even import a paper wallet and private key in Bitcoin Core. If I down load the complete blockchain will the Bitcoin Core work properly ?

Thanks for your help.

What's the error showing?

You probably can't sign a message because you're trying to use a bech32 address (address that starts with bc1) to sign.

A workaround would be to go to the console (Windows -> Console or CTRL+T) and type the following[1]:

getnewaddress ("",legacy)

and then sign a message using the generated address.

[1] https://bitcoincore.org/en/doc/0.19.0/rpc/wallet/getnewaddress/

[tranthidung]

Bitcoin Core does not support seed phrase but you can get private key from your Blockchain.com wallet, and import it into Bitcoin Core or Electrum wallet.

• [Guide] Use CPFP if your stucked transactions from blockchain.com wallet
• Similar steps as written in that topic.
• I don't know Blockchain.com wallet supports to export private key or not, if it does not support, you can import it to Electrum first and from Electrum, you can get private key. Use private key to import it to Bitcoin Core. A little bit indirect solution.

[NeuroticFish]

Does its mean if the Bitcoin Core is fully downloaded and synced, the import functionalities do not work ?

If not synced the funds will not be shown properly, creating/sending out transactions will also not work.

I created few wallets in Bitcoin Core but I'd does not allow me to sign or verify messages. I could not even import a paper wallet and private key in Bitcoin Core. If I down load the complete blockchain will the Bitcoin Core work properly ?

Signing, verifying should work. I think that importing too. So, as said, please give more details on the errors you've got.


LE: Just a thought: are you trying, by chance, to use wallets taken or bought from the internet?!?

[BitMaxz]

I could not even import a paper wallet and private key in Bitcoin Core. If I down load the complete blockchain will the Bitcoin Core work properly ?

How did you exactly import the paper wallet or private key?
If your bitcoin core is prune you can't able to use the import function you need to disable prune mode to be able to import paper backup.

If you downloaded and completely fully synced most of the function under console will work except if your core is pruned.

[Husna QA]

I have a Wallet in Blockchain.Com. I want import it to my Bitcoin Core QT. It is not allowing me to import it. Can anyone assist me and guide me step by step to import my Bitcoin Address ?

Thank you for your help.

FIRST STEP
Backup seed phrases on https://www.blockchain.com/ (skip this step if you have already backed it up).

- Login to https://www.blockchain.com/, then at the account, go to "Security" settings.



- In "Secret Private Key Recovery Phrase", click "Backup", then click "View Secret Private Key Recovery Phrase".





- Save the recovery phrase.




SECOND STEP
Convert BIP39 mnemonic phrases to private keys.

- Download bip39-standalone.html (standalone offline version) here:
https://github.com/iancoleman/bip39#standalone-offline-version



- Then TURN OFF INTERNET ACCESS.
- Open the file "beep39-standalone.html" (offline).
- In the "BIP39 Mnemonic" column, fill in the recovery phrase obtained from https://www.blockchain.com/.



- Scroll to the bottom. In "Derived Addresses", save the Private Key of the Bitcoin address you created on https://www.blockchain.com/.



- Close the "beep39-standalone.html" file and re-enable internet access.


THIRD STEP
Import the Private key to Bitcoin Core.

- Run Bitcoin Core, then open "Console" via the "Window" menu.

- In the input field type: importprivkey "privkey" (the contents of the private key previously obtained from "beep39-standalone.html" ). Then the Rescanning (Wallet) will appear.

Code:

importprivkey xxxxxx

- Go to "Window" -> "Receiving addresses" to see the Bitcoin Address that has successfully imported with the private key.

[nc50lc]

I have a Wallet in Blockchain.Com. I want import it to my Bitcoin Core QT. It is not allowing me to import it. Can anyone assist me and guide me step by step to import my Bitcoin Address ?

Aside from individual private keys (above), can also import the "master private key" to import the whole wallet while keeping the HD feature.
For that, you'll need to create a blank "descriptor wallet" and import a descriptor made from your backup phrase's master private key.

Here are the steps:

• Follow Husna QA's instructions up to the point when you paste your backup phrase to iancoleman's BIP39 tool.
• But instead of going through the private keys, copy the "BIP32 Root Key" instead, should start with "xprv".
• Generate a Parent Descriptor using that master key by following this format:

  For your wallet with legacy Bitcoin Addresses: "pkh(xprv...........nFG3cCzejXfUUzMWehii19K/44'/0'/0'/0/*)"

  For your wallet with SegWit Bitcoin Addresses: "wpkh(xprv...........nFG3cCzejXfUUzMWehii19K/84'/0'/0'/0/*)"

• Open Bitcoin Core and create a new wallet and tick the options "Descriptor Wallet" and "Blank Wallet", the other option should be unchecked.
• Open the console (Window->Console) and use the command "getdescriptorinfo" followed by the descriptor that you created, take note of the "checksum" among the results.
• Now select the correct wallet in the drop-down menu above the console and import the descriptor using this format (example):

  importdescriptors "[{\"desc\": \"pkh(xprv8ZgxM...your descriptor..Wehii19K/44'/0'/0'/0/*)#checksum\",\"timestamp\": \"0\",\"active\": true,\"internal\": false,\"range\": [0,999]}]"

  (your descriptor starts from pkh and ends before the checksum)
  (replace the "#checksum" with the checksum from the result of getdescriptorwallet)
  
  
• Wait for it to finish the rescan and your funds should appear.
  
  

Note: Since this will only import a descriptor for receiving addresses, your wallet won't be able to create transactions if it needs a change.
To fix that, you should import a descriptor for change addresses or manually indicate a change address when sending bitcoins.
It's also recommended to use a blank wallet since this will deactivate the current active parent descriptor (but will not delete/replace) if imported to an existing descriptor wallet.

Lastly: Just like what's been suggested by others, it's still best to just send the funds to your Bitcoin Core wallet .

[Welsh]

I don't know exactly what your reasons are, but if you plan on making a offline wallet with Bitcoin Core, don't import the private keys like above, since those private keys have already touched the internet, and potentially been exposed. I'm not sure how Blockchain.com store their private keys either, so they may well have been compromised from the beginning. I'd honestly whatever way you want to go about it, just generate a new wallet, pay the fee to send the transaction, and be at ease that you've generated that wallet securely, rather than relying on maybes from Blockchain.com's side.

I created few wallets in Bitcoin Core but I'd does not allow me to sign or verify messages. I could not even import a paper wallet and private key in Bitcoin Core.

You should be able too regardless. Walk us through the steps that you're taking, and we might be able to help. Remember that white spaces count etc. It needs to match, exactly.

[DireWolfM14]

Husna QA's instructions will work, but this begs the question: Why?

A web wallet is considered among the least secure wallets in bitcoin country.  The private keys are all stored and accessible by Blockchain.info, and even if you no longer use the web service, your wallet would still be stored on their server.  If their security gets compromised and a hacker my be able to access your private keys.  This could still happen years from now.

If your goal is to use a desktop wallet to create transactions, an easy way to do so is to restore your Blockchain.info wallet in Electrum using the Bip39 option.  If your goal is secure your funds, you should create a new wallet using whatever desktop application you're comfortable using.

[Husna QA]

Husna QA's instructions will work, but this begs the question: Why?

A web wallet is considered among the least secure wallets in bitcoin country.  The private keys are all stored and accessible by Blockchain.info, and even if you no longer use the web service, your wallet would still be stored on their server.  If their security gets compromised and a hacker my be able to access your private keys.  This could still happen years from now.

If your goal is to use a desktop wallet to create transactions, an easy way to do so is to restore your Blockchain.info wallet in Electrum using the Bip39 option.  If your goal is secure your funds, you should create a new wallet using whatever desktop application you're comfortable using.

I don't know if the wallet and the seed phrase are from Blockchain.com safe or not.
I use hardware wallets to store cryptocurrency assets and don't trust web wallets because hacks can happen at any time.

When the OP or anyone imports a seed phrase from Blockchain.com into a desktop wallet like Bitcoin Core, it means that at the same time, he has the same two wallets that can be accessed through those two types of wallets. So the wallet security gap in the web wallet is still vulnerable to being hacked even though it has been imported into Bitcoin Core.

It is better to use a new address on a more secure wallet.

[BitMaxz]

I don't know if the wallet and the seed phrase are from Blockchain.com safe or not.
I use hardware wallets to store cryptocurrency assets and don't trust web wallets because hacks can happen at any time.

When the OP or anyone imports a seed phrase from Blockchain.com into a desktop wallet like Bitcoin Core, it means that at the same time, he has the same two wallets that can be accessed through those two types of wallets. So the wallet security gap in the web wallet is still vulnerable to being hacked even though it has been imported into Bitcoin Core.

It is better to use a new address on a more secure wallet.

That always has a big risk having two wallets with the same Backup seed or even extracting the private key from the Blockchain wallet and importing it to the Bitcoin core wallet has a risk.
Like you said it's a web wallet any device with a wallet generated by seed online is always vulnerable to any online hacking/hijacking attacks.
In both Blockchain and Bitcoin core wallets if your device is connected to the internet there are still possibilities that all of your private keys can be hacked/hijacked that is why a Hardware wallet was built to avoid such vulnerabilities.


Or if you don't have a budget to have a hardware wallet then having an offline/cold wallet is the best option just make sure never connected your device to the internet and the wallet must be generated on the same offline device.

[allcom]

Hi, do you think Bitcoin core is not secure? I am having difficulties finding that answer.
Example: A dedicated computer that 99,99% of the time is off. This computer has only one purpose, to keep a full node of btc and also has created 2 wallet #1 and #2. This computer for hardware has encrypted disk's with 2 set of raid 10 for backing up the backup wallet file. Extracting from disk this file has been tested successful.  Firewall has only one "allow" that is btc core everything else is blocked. And ofc both wallets are encrypted. So why a ledger USB is consider more secure then BTC core?

On this scenario there is a second computer also with btc core and also full node. This computer is always online (also has firewall that block everything except core btc). The purpose of this computer is to use the "importprivkey" of the wallet #2 that was created on this first computer so it can "receive" btc and then "send" them to wallet #1. Both computers dog have USB ports so the "importprivkey" is written down letter by letter.
But the "importprivkey" on the second computer do note restore the wallet #2.

Wallet was created on computer #1 and the "Descriptor Wallet" option was checked.
The Address was created "Base58 (PSH-SegWit)

Before using "importprivkey" on computer #2 a wallet with "Make Blank Wallet" ,check was created (i also tried a wallet with only "Descriptor Wallet" checked). Why this method do not restore the wallet and the address (public) on computer #2?

Thank you in advanced.

[nc50lc]

But the "importprivkey" on the second computer do note restore the wallet #2.

Wallet was created on computer #1 and the "Descriptor Wallet" option was checked.
The Address was created "Base58 (PSH-SegWit)

The computers' names are quite misleading, there's "second computer" and there's "wallet #2".
Do you mean "address #2"? Because "addresses" aren't "wallets", the loaded Bitcoin Core wallet(s) is your wallet.
With that, try to name them: "computer 1", "computer 2", "address 1", "address 2"... etc.

Anyways, since it's descriptor, how did you managed to export the private key?
Because dumpprivkey command wont work on it (there's a workaround but I'd like to ask how you did it)

Before using "importprivkey" on computer #2 a wallet with "Make Blank Wallet" ,check was created (i also tried a wallet with only "Descriptor Wallet" checked). Why this method do not restore the wallet and the address (public) on computer #2?

Thank you in advanced.

Descriptor wallets do not support importprivkey command.
If you want to import a single private key to a descriptor wallet, you should use importdescriptor command instead.

For P2SH-SegWit, the descriptor should be in this format (with sample RegTest prvKey):

Code:

sh(wpkh(cT7NyuTsgPtTBF91g1vbdzRJ4C1KHffKJpMXExTYjmJTRHcBMJfE))

To import it using importdescriptor command, it should be in this format:

Code:

importdescriptors "[{\"desc\": \"sh(wpkh(cT7NyuTsgPtTBF91g1vbdzRJ4C1KHffKJpMXExTYjmJTRHcBMJfE))#fjl3gf6p\",\"timestamp\": 0,\"label\": \"address #2\"}]"

"#fjl3gf6p" is the checksum which you can get from getdescriptorinfo command, e.g.:

Code:

getdescriptorinfo "sh(wpkh(cT7NyuTsgPtTBF91g1vbdzRJ4C1KHffKJpMXExTYjmJTRHcBMJfE))"

For non-descriptor wallets, all three address types will be derived from the imported private key, including P2SH-SegWit.
Try to add a label to see if it's actually not imported (e.g.: importprivkey "prbvKey" "address #2");
In case the P2SH-SegWit address is different, you may be importing the wrong prvKey.
BTW, although there's a conversation here about how to import to Bitcoin Core, the question is quite off-topic.
I'd suggest you to create a new topic in case you need a follow-up to your question.

[allcom]

Thank you for your time and help it is very impressive this day that forums still exist.
Computer #1 has created Wallet #1 and Wallet #2. Each wallet have created a new address using "Base58 (PSH-SegWit)".
Using the command dumpprivkey on Wallet #2 i got the private key for the public key (aka address) of this wallet. The public key (aka address) is a 3Mhxxxxx .
Next on Computer #2 i  created a new wallet using "Make Blank Wallet" check box enable. It confirmed the blocks and in deed i have an history of the transaction of this address but the available balance btc is 0.000000 . And when i press receive there is no address there, but when i press Window\Receiving addresses i can see 3 address
1. start with 15z xxxx
2. start with 3Mh xxxx and is the address i used to receive BTC on computer #1 on wallet #2 that has the exact address  i also used  dumpprivkey.
3. 3Nft xxxxx

[nc50lc]

-snip- It confirmed the blocks and in deed i have an history of the transaction of this address but the available balance btc is 0.000000 .
And when i press receive there is no address there, but when i press Window\Receiving addresses i can see 3 address
1. start with 15z xxxx
2. start with 3Mh xxxx and is the address i used to receive BTC on computer #1 on wallet #2 that has the exact address  i also used  dumpprivkey.
3. 3Nft xxxxx

That's the expected 'Receive' tab behavior for blank wallets since those rely on active 'hdseed' or active ranged descriptor to generate new addresses from.
Since it's available in your receiving addresses list, the private key is imported successfully.

As for the imported key, the balance should've reflected based from the transactions that it scanned.
If it's zero, it's either the transaction are all spent or it failed to scan some of the transactions.
For the latter, you can try to rescan the blockchain using the command: rescanblockchain

[allcom]

-snip-
If it's zero, it's either the transaction are all spent or it failed to scan some of the transactions.
For the latter, you can try to rescan the blockchain using the command: rescanblockchain

On Computer #1 (where the wallet with the address was created) the balance is correct (not 0.000000) and i have run the rescanblockchain command many times without success. Something is not working on this latter's versions of core btc. I don't want to use restore wallet from backup since it will compromise the security that a private kay offers.

[nc50lc]

On Computer #1 (where the wallet with the address was created) the balance is correct (not 0.000000) and i have run the rescanblockchain command many times without success. Something is not working on this latter's versions of core btc.

The fact that it's already in your receiving address list tells that it's imported successfully.
So the main issue is either there's a transaction that Bitcoin Core failed to scan in Computer2, or the transaction in Computer1 isn't actually in the Blockchain,
only locally saved in the wallet for a couple of possible reasons like dropped, replaced, invalid or not broadcasted.

Hi, do you think Bitcoin core is not secure? I am having difficulties finding that answer.
Example: A dedicated computer that 99,99% of the time is off. This computer has only one purpose, to keep a full node of btc and also has created 2 wallet #1 and #2. This computer for hardware has encrypted disk's with 2 set of raid 10 for backing up the backup wallet file. Extracting from disk this file has been tested successful.  Firewall has only one "allow" that is btc core everything else is blocked. And ofc both wallets are encrypted. So why a ledger USB is consider more secure then BTC core?

I think this whole issue really needs its own topic since there's more to it than failing to import a private key to another computer.
For example, computer1 doesn't have to be 99.99% off, it just have to be "AirGap";
And computer 2 doesn't have to be imported with a private key from Computer1, it only needs a watching-only descriptor.
What described is a Cold-Storage Setup which is a lot safer than Hardware Wallets.

You can start a topic by going to the proper board, recommended: Bitcoin Forum > Bitcoin > Bitcoin Technical Support
And by clicking the small blue "new topic" button at the right-hand side of the page.