Initial Block Download (IBD)

Initial Block Download (IBD) is the one-time process a brand-new Bitcoin full node performs when it first comes online: downloading every block from the genesis block to the current chain tip and independently validating each one against the consensus rules. Only after IBD completes is the node fully synced and able to verify payments on its own. It is the price of admission for trustless verification.

What happens during IBD

The node connects to peers, fetches the chain of block headers first, then downloads the full blocks and checks every transaction: valid signatures, no double-spends, no inflation beyond the schedule, correct proof-of-work. As of 2026 this means processing ~600+ GB of historical data and hundreds of millions of transactions. Depending on hardware, bandwidth, and settings, IBD can take anywhere from several hours to a few days. To speed it up, nodes use assumevalid (skipping signature checks on deeply-buried historical blocks while still checking everything else) — a default that can be disabled for fully-from-scratch validation.

Why it matters for sovereignty

IBD is what makes "don't trust, verify" literal. By validating the entire history itself, your node never has to trust anyone's claim about the state of the ledger. A pruned node performs the same full IBD validation but then discards old block data to save disk, keeping the trust guarantee while shrinking the footprint.

IBD is the startup cost of running a full node such as Bitcoin Core; once complete, the node only needs to validate each new block as it arrives.