Importing wallet.dat ?

[OmegaStarScream]

Now and after I upgraded to Windows 10  & as some of you have seen my old threads here and know the high Paranoïa that I have ... I made a blockchain.info wallet , I sent about 0.25 BTC to that wallet which means I have only one address on that account for now .

Beside the 0.25 BTC which are on my btc wallet , I have a backup of my wallet from Bitcoin Core .
I need to basically send funds to my Electrum wallet and I know I could do the following :

for the 0.25 BTC I could just send it but for the .dat it's something else because Electrum don't allow importing it .

I could import wallet.dat to Blockchain.info https://blockchain.info/fr/wallet/import-wallet from here but why It doesn't require connecting to my account there ?

And If I manage to import it , will I have all addresses that I had on .dat to my Blockchain.info account ? I mean I can sign messages from my Blockchain.info of all addresses I had on Bitcoin Core ?



Or .. is there is any wallet.dat reader ? basically convert it to string or something so I can read it using Notepad and I copy private keys and do whatever I need to ?

Gracias amigos 

[1714131767]

1714131767

[1714131767]

1714131767

[1714131767]

1714131767

[hexafraction]

Or .. is there is any wallet.dat reader ? basically convert it to string or something so I can read it using Notepad and I copy private keys and do whatever I need to ?

Gracias amigos 

Yes, if you import it back into a fresh bitcoin-qt installation, you can use dumpprivkey.

And If I manage to import it , will I have all addresses that I had on .dat to my Blockchain.info account ? I mean I can sign messages from my Blockchain.info of all addresses I had on Bitcoin Core ?

Yes.

[OmegaStarScream]

Or .. is there is any wallet.dat reader ? basically convert it to string or something so I can read it using Notepad and I copy private keys and do whatever I need to ?

Gracias amigos 

Yes, if you import it back into a fresh bitcoin-qt installation, you can use dumpprivkey.

And If I manage to import it , will I have all addresses that I had on .dat to my Blockchain.info account ? I mean I can sign messages from my Blockchain.info of all addresses I had on Bitcoin Core ?

Yes.

No mate (for your first answer) , I need something else because Bitcoin Core is totally screwed on my PC and takes always time to reindex which doesn't really worth it I'am looking for something fast .

for your second answer , well I don't have option to import .dat on my blockchain.info account , I only have that link from google to the Import wallet.dat page and if I import , how it will get linked to my account that I already have ? 

[Muhammed Zakir]

-snip-
I could import wallet.dat to Blockchain.info https://blockchain.info/fr/wallet/import-wallet from here but why It doesn't require connecting to my account there ?

Blockchain.info will create a new account when you import wallet.dat file. AFAIK, you can't import wallet.dat file to an existing wallet.

And If I manage to import it , will I have all addresses that I had on .dat to my Blockchain.info account ? I mean I can sign messages from my Blockchain.info of all addresses I had on Bitcoin Core ?

Wallet.dat backed up will contain all addresses. But, if you have a backup of wallet.dat before you used 100 addresses, then you need to get a new backup of wallet.dat.

P.S. I missed your later question. Yes, you can sign any message using all the addresses you own which you had on Bitcoin Core.

The Bitcoin-Qt/bitcoind client's keypool has by default 100 Bitcoin addresses. Each spend transaction that has change chews up one of those addresses. Additionally each click on New Address will consume an address from the keypool as well. So you should be able to get by without a new backup until after 100 spend transactions plus any requests for a New Address.

So if you do 10 spend transactions a month, and receive funds 5 times a month you would be fine with a backup every 4 months maybe.

A backup plan should consider that backups fail, so multiple backups don't hurt anything.

The size of the keypool can be configured so that frequent use can occur without having to make backups as frequently. For instance, weekly backups would be fine for a wallet that does 100 transactions a week but the keypool has size of 250.

When the wallet is encrypted, no keys are added to the pool until an action that requires the passphrase to be entered. Backup strategy should take this into account.

And finally, if you import a private key, that key will not exist in any previously made backups.

Or .. is there is any wallet.dat reader ? basically convert it to string or something so I can read it using Notepad and I copy private keys and do whatever I need to ?

Gracias amigos 

You can use Pywallet. In fact, I recommend it. https://bitcointalk.org/index.php?topic=34028.0

I recommend you to dump private keys using Pywallet and then, sweep Bitcoins from it to Electrum or create a new Electrum wallet to import those private keys. If you still insist to use Blockchain.info, click "Import / Export", click "Import Wallet" and then paste the output you got after running pywallet.py --dumpwallet.

[Deathwing]

When you import a wallet.dat to Blockchain, all the addresses that was included with the wallet.dat gets recorded to your Blockchain.info wallet, If you want you can transfer the funds to a different address.

Or you can use Multibit

[OmegaStarScream]

As usual Muhammed Zakir save the situation . Thank you so much mate , I really appreciate what you are doing to the community .
I also sent you 5$ as a thanks I hope the address on your profile is the right one .

@Deathwing  Pretty sure that Multibit don't read wallet.dat either .

[Muhammed Zakir]

As usual Muhammed Zakir save the situation .

It will be helpful if you can cut this out from your posts. People might think you are an alt of mine.

Thank you so much mate , I really appreciate what you are doing to the community .
I also sent you 5$ as a thanks I hope the address on your profile is the right one .

It was not needed. Anyway, thank you!