<blockquote>
  <p>As long as the wallet is in place before bitcoin core has a chance to
  prune anything, it will work properly<br>
  <a href="https://bitcointalk.org/index.php?topic=1375633.0;prev_next=next" rel="nofollow noreferrer">Reference Link</a></p>
</blockquote>

<p>Let me explain. Basically here is a simplified version of how bitcoind stores wallet transactions:</p>

<ul>
<li><em>wallet.dat</em> contains <em>Private Keys | Synced upto Block | Wallet transactions</em></li>
<li>When new block arrives, bitcoind looks for wallet transactions in the block and adds the ones found into  <em>wallet.dat</em> and also updates <em>Synced upto Block</em> field</li>
<li>In prune mode, older block data is removed, nothing happens to <em>wallet.dat</em></li>
</ul>

<p>So if you activate prune mode on a running node, or boot up an old bitcoin node everything should work.<br>
However, if you import an older <em>wallet.dat</em> into already running pruned node, it has to rescan everything from <em>Synced upto Block</em> to find the transactions. This may not be possible due to missing block data</p>

CC BY-SA 3.0
2018-03-20T12:11:14.150Z
2018-03-20T13:11:20.443Z
2018-03-20T13:11:20.443Z
dark knight
<p>I have bitcoind running in prune mode (last 10000MiB). Will daemon have info about all my wallet’s transactions or just those that will fit 10000MiB tail?</p>

<bitcoind>
Will bitcoind save all wallet transactions in prune mode?
Kirzilla
# Will bitcoind save all wallet transactions in prune mode?

(Asked by: username_0 on 2018-03-20)

I have bitcoind running in prune mode (last 10000MiB). Will daemon have info about all my wallet’s transactions or just those that will fit 10000MiB tail?

**Tags:** bitcoind


---

## 1 answers

### Answer by username_1 on 2018-03-20. Score: 4 | Accepted answer

> As long as the wallet is in place before bitcoin core has a chance to
> prune anything, it will work properly  
> [Reference Link](https://bitcointalk.org/index.php?topic=1375633.0;prev_next=next)

Let me explain. Basically here is a simplified version of how bitcoind stores wallet transactions:

* *wallet.dat* contains *Private Keys | Synced upto Block | Wallet transactions*
* When new block arrives, bitcoind looks for wallet transactions in the block and adds the ones found into *wallet.dat* and also updates *Synced upto Block* field
* In prune mode, older block data is removed, nothing happens to *wallet.dat*

So if you activate prune mode on a running node, or boot up an old bitcoin node everything should work.  
However, if you import an older *wallet.dat* into already running pruned node, it has to rescan everything from *Synced upto Block* to find the transactions. This may not be possible due to missing block data


---

