<p>Try <strong>not</strong> to reuse keys/addresses.</p>

<p>Just call <code>getnewaddress</code> 200-times (RPC call in a loop).</p>

<p>Maybe call <code>keypoolrefill</code> afterwards (and do a backup again if you don't use HD [Core >=0.14]).</p>

CC BY-SA 3.0
2017-04-09T19:24:33.107Z
2017-04-09T19:24:33.107Z
Jonas Schnelli
<p>I have a wallet running on a raspbery pi and the SD card hit the skids, fortunatley I have a backup of the .iso from 1 month ago so I have recovered the entire state as of that time.</p>

<p>My only concern is over the keypool.  I had increasead it to 1000 because I was testing issung a lot of transactions, my keypool was down to around 800 before my issue required the backup.  Now my keypool is at 970 (as it was a month ago) and Im trying to figure out if thats going to cause a problem when a key that is already used in an existing TX is to be used again?</p>

<wallet.dat>
keypool and restoring from backup
Scalextrix
# keypool and restoring from backup

(Asked by: username_0 on 2017-04-07)

I have a wallet running on a raspbery pi and the SD card hit the skids, fortunatley I have a backup of the .iso from 1 month ago so I have recovered the entire state as of that time.

My only concern is over the keypool. I had increasead it to 1000 because I was testing issung a lot of transactions, my keypool was down to around 800 before my issue required the backup. Now my keypool is at 970 (as it was a month ago) and Im trying to figure out if thats going to cause a problem when a key that is already used in an existing TX is to be used again?

**Tags:** wallet.dat


---

## 1 answers

### Answer by username_1 on 2017-04-09. Score: 1

Try **not** to reuse keys/addresses.

Just call `getnewaddress` 200-times (RPC call in a loop).

Maybe call `keypoolrefill` afterwards (and do a backup again if you don't use HD [Core >=0.14]).


---

