# Bitcoin wallet rescan versus node reindex A wallet rescan searches available blockchain data for transactions relevant to known wallet keys or scripts. Reindexing rebuilds node databases from block files; reindex-chainstate has a narrower state-rebuild purpose in Core. These operations solve different problems and do not recreate a lost private key. Choose the documented operation for the actual error and installed version before initiating a lengthy rebuild. Evidence: [rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/); [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp); [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-rescan-vs-reindex/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Rescan target:** Wallet-related transaction discovery ([rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/)) - **Reindex target:** Node state and block/index databases ([Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp)) - **Not recovered:** Missing signing secrets ([Wallets](https://developer.bitcoin.org/devguide/wallets.html)) ## Identify the missing or damaged information Core stores block bodies, chainstate and wallets in separate places. If a wallet already knows a relevant script but has not searched the period when it received funds, a rescan can discover the transactions. It is not the same as rebuilding consensus state for every wallet. If the node reports damaged chain databases, the appropriate recovery may involve reindexing. The cited v29.0 help defines reindex as rebuilding chainstate, block index and active optional indexes from block files. Evidence: [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md); [rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/); [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp) ## A scan range can be smaller than the whole history Suppose the earliest possible payment is at height 800,000 and the node has processed height 850,000. A documented scan from 800,000 through 850,000 covers 50,001 block heights inclusively. A mistaken start height after the receipt can miss it. The RPC reports where scanning began and ended. Available block filters can speed a descriptor-wallet scan in the documented configuration, but speed is not proof that the wallet’s script or derivation information is complete. Evidence: [rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/) ## Pruning and backups affect the recovery path A pruned node may lack the historical block bodies required for a chosen operation. Core v29.0 explicitly treats pruning and reindex-chainstate as incompatible; a full rebuild path can require reacquiring data. Follow the installed release’s guidance rather than copying an old command blindly. Preserve wallet recovery material before invasive maintenance. Neither downloading the chain again nor rebuilding its index can manufacture a key that no remaining backup contains. Evidence: [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp); [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md); [Securing your wallet](https://bitcoin.org/en/secure-your-wallet) ## Questions ### Will reindexing fix an incorrect seed or derivation path? No. Reindexing rebuilds node data. The wallet must still contain the correct keys, scripts and derivation information before a scan can identify and spend the intended outputs. Evidence: [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp); [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) ### Does a rescan send a Bitcoin transaction? No. It searches local chain data for wallet-related history. It does not itself move funds, sign a payment or pay a network fee, although it can consume local computing resources. Evidence: [rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/) ## Claims and scope ### bitcoin-rescan-vs-reindex-quick-answer A wallet rescan searches available blockchain data for transactions relevant to known wallet keys or scripts. Reindexing rebuilds node databases from block files; reindex-chainstate has a narrower state-rebuild purpose in Core. These operations solve different problems and do not recreate a lost private key. Choose the documented operation for the actual error and installed version before initiating a lengthy rebuild. Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02. Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-rescan-vs-reindex-fact-rescan-target Rescan target: Wallet-related transaction discovery Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-rescan-vs-reindex-fact-reindex-target Reindex target: Node state and block/index databases Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-rescan-vs-reindex-fact-not-recovered Not recovered: Missing signing secrets Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/) — Bitcoin Core. Rescan local blocks for wallet-related transactions within a height range. Locator: Description; Arguments; Result. Retrieved: 2026-10-02T18:53:55.698Z. - [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp) — Bitcoin Core. Definitions of reindex/chainstate rebuild and node configuration switches. Locator: SetupServerArgs: assumevalid, reindex, reindex-chainstate, prune, listen, server; prune/reindex-chainstate compatibility check. Retrieved: 2026-10-02T18:53:55.958Z. - [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) — Bitcoin 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. Retrieved: 2026-10-02T18:53:55.926Z. - [Wallets](https://developer.bitcoin.org/devguide/wallets.html) — Bitcoin developer documentation. Wallet types, generated keys, deterministic wallets and offline signing. Locator: Wallet Programs; Full-Service Wallets; Signing-Only Wallets; Wallet Files; Hierarchical Deterministic Key Creation; Loose-Key Wallets. Retrieved: 2026-10-02T18:53:53.756Z. - [Securing your wallet](https://bitcoin.org/en/secure-your-wallet) — Bitcoin.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.659Z. - [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) — Bitcoin Improvement Proposals. Deterministic key derivation, backup scope and public/private child derivation. Locator: Motivation; Extended keys; Security. Retrieved: 2026-10-02T18:53:54.013Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Bitcoin wallet rescan versus node reindex.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-rescan-vs-reindex/