<p>Unfortunately, the method used to generate new keys at the time was to generate them randomly and store them in the <code>wallet.dat</code> file. So if you don't have a backup of the file <em>after</em> the address was used, it is not guaranteed that your backups will have the necessary key.</p>
<p>I would suggesting dumping the <code>wallet.dat</code> file to see all the private keys contained within it. Either it has the key for the address the funds were sent to and you are in luck or it doesn't and you are out of luck.</p>
<p>One easy way to do this is to use the <code>dumpwallet</code> command. There are also tools available to parse a wallet file and extract all the keys in it.</p>

CC BY-SA 4.0
2020-08-04T17:04:06.263Z
Someone on Reddit informed me that Bitcoin Core versions during this time period generated their keys deterministically (seeded from the initial private key), and therefore I should be able to regenerate them. So far this has proved false.
throwaway647723
CC BY-SA 4.0
2020-08-04T16:53:44.780Z
2020-08-04T16:53:44.780Z
David Schwartz
<p>I’m seeking help from the Bitcoin community to recover lost funds from a wallet.dat file. Someone I know asked me to help recover their lost funds - but I’m stumped and now seeking help from the experts.</p>
<p>Facts</p>
<ul>
<li>A wallet.dat file was created in approximately July 2017
<ul>
<li>Ubuntu Linux (v17.10?)</li>
<li>Bitcoin Core QT (v0.16.2?)</li>
<li>The original wallet.dat file was backed up and remains accessible</li>
</ul>
</li>
<li>Bitcoin was purchased on Coinbase and sent offsite to an initial receiving address within this wallet</li>
<li><em>A few months pass…</em></li>
<li>Additional bitcoin is purchased on Coinbase and sent offsite to NEWLY GENERATED receiving addresses (99% sure the same wallet)</li>
<li><em>A few years pass…</em></li>
<li>The person now wants to send their funds back to Coinbase for sale</li>
<li>They have the original wallet.dat file, but Bitcoin Core software only displays one receiving address (the initial one)</li>
</ul>
<p>Problems</p>
<ul>
<li>The wallet.dat file was backed up ONLY ONCE, and PRIOR to the generation of those additional receiving addresses</li>
<li>The device used to create the new receiving addresses cannot be found!</li>
<li>Loading the wallet.dat file into current Bitcoin Core software does not display the subsequent transactions or receiving addresses! Only the initial receiving address!</li>
</ul>
<p>Questions</p>
<ul>
<li>Can the funds for all transactions be recovered?</li>
<li>What about the funds which were sent to the new receiving addresses, which were created POST BACKUP of the wallet.dat file?</li>
<li>BONUS: If they can be recovered, what’s the best software to accomplish this, and can it also be done for the Bitcoin Cash which presumably remain associated to this wallet.dat file? Ideally without re-syncing the whole blockchain.</li>
</ul>
<p>I was under the impression that the wallet.dat file contained a private key which corresponds to any / all newly created receiving addresses, but I must be mistaken.</p>
<p>Any advice would be greatly appreciated. The person is at a dead end and I'm fresh out of ideas.</p>
<p>Thank you</p>

<bitcoin-core><wallet-recovery>
Wallet Recovery Help
throwaway647723
# Wallet Recovery Help

(Asked by: username_0 on 2020-08-04)

I’m seeking help from the Bitcoin community to recover lost funds from a wallet.dat file. Someone I know asked me to help recover their lost funds - but I’m stumped and now seeking help from the experts.

Facts

* A wallet.dat file was created in approximately July 2017
  + Ubuntu Linux (v17.10?)
  + Bitcoin Core QT (v0.16.2?)
  + The original wallet.dat file was backed up and remains accessible
* Bitcoin was purchased on Coinbase and sent offsite to an initial receiving address within this wallet
* *A few months pass…*
* Additional bitcoin is purchased on Coinbase and sent offsite to NEWLY GENERATED receiving addresses (99% sure the same wallet)
* *A few years pass…*
* The person now wants to send their funds back to Coinbase for sale
* They have the original wallet.dat file, but Bitcoin Core software only displays one receiving address (the initial one)

Problems

* The wallet.dat file was backed up ONLY ONCE, and PRIOR to the generation of those additional receiving addresses
* The device used to create the new receiving addresses cannot be found!
* Loading the wallet.dat file into current Bitcoin Core software does not display the subsequent transactions or receiving addresses! Only the initial receiving address!

Questions

* Can the funds for all transactions be recovered?
* What about the funds which were sent to the new receiving addresses, which were created POST BACKUP of the wallet.dat file?
* BONUS: If they can be recovered, what’s the best software to accomplish this, and can it also be done for the Bitcoin Cash which presumably remain associated to this wallet.dat file? Ideally without re-syncing the whole blockchain.

I was under the impression that the wallet.dat file contained a private key which corresponds to any / all newly created receiving addresses, but I must be mistaken.

Any advice would be greatly appreciated. The person is at a dead end and I'm fresh out of ideas.

Thank you

**Tags:** bitcoin-core, wallet-recovery


---

## 1 answers

### Answer by username_1 on 2020-08-04. Score: 1

Unfortunately, the method used to generate new keys at the time was to generate them randomly and store them in the `wallet.dat` file. So if you don't have a backup of the file *after* the address was used, it is not guaranteed that your backups will have the necessary key.

I would suggesting dumping the `wallet.dat` file to see all the private keys contained within it. Either it has the key for the address the funds were sent to and you are in luck or it doesn't and you are out of luck.

One easy way to do this is to use the `dumpwallet` command. There are also tools available to parse a wallet file and extract all the keys in it.

> **Comments:**
> **username_0**: Someone on Reddit informed me that Bitcoin Core versions during this time period generated their keys deterministically (seeded from the initial private key), and therefore I should be able to regenerate them. So far this has proved false.  

---

