Initial Block Download (IBD)

Initial block download, or IBD, is the process by which a new Bitcoin node downloads and verifies the entire blockchain from the network, starting at the 2009 genesis block. The node checks every signature and consensus rule across more than 600 gigabytes of history, which takes from several hours to a few days depending on hardware and bandwidth.

Why it matters

IBD is the price of trustlessness. A node that completes it has verified Bitcoin's entire monetary history itself, every coin's issuance and every transaction's validity, and afterward holds a self-audited copy of the ledger requiring nobody's word. This is what people mean by don't trust, verify: the supply cap is not a promise, it is something tens of thousands of node operators have independently checked.

The burden also shapes Bitcoin's governance. Keeping IBD feasible on ordinary hardware is a standing argument against larger blocks, since a chain too heavy to verify would concentrate validation among institutions, and it motivated engineering like assumevalid, parallel validation, and the UTXO snapshot mechanism that lets a node begin operating while history verifies in the background.

How it works

The node fetches headers first to establish the most-work chain, then downloads blocks in parallel from multiple peers, validating scripts and updating its UTXO set as it goes. Pruned nodes verify everything but discard old block data afterward, keeping full security with a few gigabytes of storage.