Wallet cache

Chain-derived state and local records

A wallet records discovered outputs, transactions and its progress through the chain. Keeping that state locally saves work on later opens. This is distinct from the node database, which stores blockchain data for network validation.

Wallet software may also retain labels, notes and outgoing-payment information locally. The exact file layout depends on the wallet. The official CLI separates its key file from the main wallet state file, but that layout should not be assumed for every mobile or hardware-wallet application.

References: CLI wallet reference · Monero source: wallet/wallet2.cpp

Recovering funds and local records

A seed backup aims to preserve spending access. A wallet-file backup can preserve records needed for accounting or troubleshooting as well. Those are different needs, and recovering one does not guarantee the other.

Before a rebuild, keep an offline protected copy and follow the wallet documentation. Choose a restore height early enough to include the wallet history. A later starting point can hide relevant outputs from the scan without removing them from the chain.

References: Monero source: wallet/wallet2.cpp · CLI wallet reference

Example

Restoring a wallet from its seed can recover chain-derived funds after a rescan, but a locally entered transaction note may be absent because it was never recorded on the blockchain.

References: Monero source: wallet/wallet2.cpp · CLI wallet reference

Limits and cautions

A cache is not a substitute for the seed, required passphrase or key backup. It can also contain sensitive history. Do not delete wallet files or send them to support simply because someone calls them a cache.

References: Monero source: wallet/wallet2.cpp · CLI wallet reference