Author

Topic: How do I import transactions, receiving and sending addresses in Bitcoin Core? (Read 634 times)

newbie
Activity: 53
Merit: 0
I've changed my HDD and I have installed new Bitcoin Core instance. I have archive of wallet.dat, transactions, sending and receiving addresses exported from old one. Copying old wallet.dat is okay, but how do I import tx's, sending and receiving addresses that are archived in .csv files? I'm not sure why Bitcoin Core has 'export' option but missing 'import' one?

Its all in the wallet.dat file. AFAIK there is no import function.
All the details? Including labels of sending and receiving addresses?
---
You're right. Everything is in there. Thanks a lot.
staff
Activity: 3458
Merit: 6793
Just writing some code
All of the receiving addresses and transactions are saved in the wallet.dat file. I think that the sending addresses are also stored there as well. To import them all, just put the file in the data directory. It may be replacing a wallet.dat file already there, but if that one is empty, you can delete it. Then when you start up Bitcoin Core, everything should be just as it were prior to you upgrade.
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
I've changed my HDD and I have installed new Bitcoin Core instance. I have archive of wallet.dat, transactions, sending and receiving addresses exported from old one. Copying old wallet.dat is okay, but how do I import tx's, sending and receiving addresses that are archived in .csv files? I'm not sure why Bitcoin Core has 'export' option but missing 'import' one?

Its all in the wallet.dat file. AFAIK there is no import function.
newbie
Activity: 53
Merit: 0
I've changed my HDD and I have installed new Bitcoin Core instance. I have archive of wallet.dat, transactions, sending and receiving addresses exported from old one. Copying old wallet.dat is okay, but how do I import tx's, sending and receiving addresses that are archived in .csv files? I'm not sure why Bitcoin Core has 'export' option but missing 'import' one?
Jump to: