Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Bitcoin basics · Entry 194

Bitcoin wallet-file backups: what a seed may not preserve

AI-assisted research · separate automated verificationCorrections

Theme
Bitcoin basics
Sources
7 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for Bitcoin wallet-file backups: what a seed may not preserve
FactDetailSource
Core backupbackupwallet copies the wallet to a destination[1]
Seed scopeDerived keys are not every possible imported key[3][5]
Local recordsWallet comments need not be on chain[6]
01

Distinguish chain data from local wallet data

Blocks can show transaction outputs and spends, but they do not necessarily contain the labels you added to your wallet. Core’s sendtoaddress documentation explicitly says its comment fields remain in the wallet rather than the transaction.

A key-only recovery can therefore locate funds without reproducing every note, contact label or accounting context. Conversely, a file containing a transaction history does not automatically contain usable spending authority.

02

Account for keys outside the main seed

Imagine a wallet with 90,000 satoshis controlled by derived keys and 10,000 controlled by a separately imported key. Restoring only the seed need not recover the imported-key portion. The visible total of 100,000 does not establish a single recovery source.

Electrum documents this distinction explicitly for imported-key wallets. The exact contents of a backup file depend on the product, so preserve its documented recovery material rather than assuming every file named wallet has the same scope.

03

Preserve compatibility and test the documented path

Use the application’s supported backup function, which can handle an active wallet database correctly, and protect the resulting copy from loss and disclosure. Record which product and format created it. Encryption can make a backup unreadable without its required password.

A software upgrade can change wallet-file format. Electrum warns that an older version may not read a file opened by a newer one. A backup is valuable only when the necessary data and a compatible recovery procedure remain available.

Direct answers

Questions people ask

Can the blockchain restore my wallet labels?

Only information actually published in transactions is on the chain. Core wallet comments, for example, are local data. Recovering key-derived transaction history does not automatically restore those local annotations.

Is copying a seed enough for a wallet with imported private keys?

Not necessarily. A seed regenerates its derived hierarchy; unrelated imported keys can require a separate backup. Identify the wallet’s actual key sources and supported export or backup method.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

A wallet-file backup preserves the data included in that wallet database; a mnemonic restores keys through its defined derivation process. These are not always equivalent. Imported keys, wallet policies and local records can need separate preservation. Use the wallet’s supported backup operation and keep the format, encryption credentials and software compatibility needed for restoration.

Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Core backup: backupwallet copies the wallet to a destination

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Seed scope: Derived keys are not every possible imported key

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Local records: Wallet comments need not be on chain

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. backupwallet RPCBitcoin Core

    Wallet backup destination and database-copy operation.

    Locator: Description; Arguments · Version / scope: Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release · Retrieved: 2026-10-02T18:53:55.850ZOpen source
  2. restorewallet RPCBitcoin Core

    Restoring a wallet from a backup file under documented options.

    Locator: Description; Arguments · Version / scope: Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release · Retrieved: 2026-10-02T18:53:55.697ZOpen source
  3. Hierarchical Deterministic WalletsBitcoin Improvement Proposals

    Deterministic key derivation, backup scope and public/private child derivation.

    Locator: Motivation; Extended keys; Security · Version / scope: Pinned BIPs revision · Retrieved: 2026-10-02T18:53:54.013ZOpen source
  4. Securing your walletBitcoin.org

    Backup scope, online exposure, offline signing, custody and software update practices.

    Locator: Be careful with online services; Backup your wallet; Encrypt your wallet; Offline wallet for savings; Hardware wallets; Keep your software up to date · Retrieved: 2026-10-02T18:53:53.659ZOpen source
  5. Frequently Asked QuestionsElectrum

    Electrum-specific sweep/import distinctions, seed recovery scope and address discovery.

    Locator: Does Electrum trust servers?; Can I import private keys from other Bitcoin clients?; Can I sweep private keys from other Bitcoin clients?; What is the gap limit?; How do I upgrade Electrum? · Retrieved: 2026-10-02T18:53:56.378ZOpen source
  6. sendtoaddress RPCBitcoin Core

    Fee subtraction changes recipient output; comments remain local metadata.

    Locator: Description; Arguments: amount, comment, comment_to, subtractfeefromamount, fee_rate; Result · Version / scope: Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release · Retrieved: 2026-10-02T18:53:55.005ZOpen source
  7. FilesBitcoin Core

    Wallet, block, chainstate and index files have different recovery purposes.

    Locator: Data directory location and chain-specific paths; Data directory layout: blocks/, chainstate/, wallets/; Multi-wallet environment and backupwallet guidance · Version / scope: Bitcoin Core v29.0 · Retrieved: 2026-10-02T18:53:55.926ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “Bitcoin wallet-file backups: what a seed may not preserve.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-wallet-file-backups/