<blockquote>
<p>Why an unknown record?</p>
</blockquote>
<p>If you have used your wallet in a newer version of Bitcoin Core and then downgraded, you may see this message as sometimes new versions of Bitcoin Core will write new records. If your wallet is particularly old and has been upgraded over time, it is possible that your wallet contains records that are no longer being used and have since been removed from the codebase.</p>
<p>It is also possible that your wallet was somehow corrupted, but if so, it is unlikely that the wallet would be opened at all.</p>
<blockquote>
<p>Would that one be the HD seed?</p>
</blockquote>
<p>No. HD seeds are not unknown records.</p>
<blockquote>
<p>Any reason to worry?</p>
</blockquote>
<p>Generally no. In some versions, the wallet will perform a silent upgrade of various wallet data which can involve writing new records. These are designed to be backwards compatible so that such upgraded wallets can still be used in older software without issue. Other upgrades that break compatibility must be done explicitly by the user via the <code>upgradewallet</code> RPC. Such upgrades have downgrade protections by using either wallet flags or a new wallet version which indicate to older software that the wallet contains new critical information and should not be opened if that version does not know about those versions.</p>
<p>Old records are occasionally deprecated and are no longer used by the software. These are typically added to a list of known but unused records to avoid this warning, but it is possible that this was forgotten for some.</p>

CC BY-SA 4.0
2021-11-14T21:48:50.423Z
2021-11-14T21:48:50.423Z
Ava Chow
<p>I noticed that loading this wallet:</p>
<pre><code>loadwallet ...wallet name...
</code></pre>
<p>The wallet is a 169900 legacy wallet.</p>
<blockquote>
<p>2021-..-..T..:..:..Z [...wallet name...] Keys: 0 plaintext, 4355 encrypted, 4355 w/ metadata, 4355 total. Unknown wallet records: 1</p>
</blockquote>
<p>Why an unknown record?<br />
Would that one be the HD seed?<br />
Any reason to worry?</p>

<bitcoin-core><wallet><wallet.dat>
Getting "Unknown wallet records: 1" on loading wallet
Mercedes
# Getting "Unknown wallet records: 1" on loading wallet

(Asked by: username_0 on 2021-11-14)

I noticed that loading this wallet:

```
loadwallet ...wallet name...

```

The wallet is a 169900 legacy wallet.

> 2021-..-..T..:..:..Z [...wallet name...] Keys: 0 plaintext, 4355 encrypted, 4355 w/ metadata, 4355 total. Unknown wallet records: 1

Why an unknown record?  
Would that one be the HD seed?  
Any reason to worry?

**Tags:** bitcoin-core, wallet, wallet.dat


---

## 1 answers

### Answer by username_1 on 2021-11-14. Score: 2 | Accepted answer

> Why an unknown record?

If you have used your wallet in a newer version of Bitcoin Core and then downgraded, you may see this message as sometimes new versions of Bitcoin Core will write new records. If your wallet is particularly old and has been upgraded over time, it is possible that your wallet contains records that are no longer being used and have since been removed from the codebase.

It is also possible that your wallet was somehow corrupted, but if so, it is unlikely that the wallet would be opened at all.

> Would that one be the HD seed?

No. HD seeds are not unknown records.

> Any reason to worry?

Generally no. In some versions, the wallet will perform a silent upgrade of various wallet data which can involve writing new records. These are designed to be backwards compatible so that such upgraded wallets can still be used in older software without issue. Other upgrades that break compatibility must be done explicitly by the user via the `upgradewallet` RPC. Such upgrades have downgrade protections by using either wallet flags or a new wallet version which indicate to older software that the wallet contains new critical information and should not be opened if that version does not know about those versions.

Old records are occasionally deprecated and are no longer used by the software. These are typically added to a list of known but unused records to avoid this warning, but it is possible that this was forgotten for some.


---

