BITCOIN MAINNETLive explorer status
NO ONE IN CHARGE

Initial block download (IBD)

A new Bitcoin node must download and verify every block since 2009 before it is caught up. Learn what initial block download involves and how to speed it up.

Catching up on history

A brand-new node knows only the The genesis block. To reach today, it must fetch and verify every block since 2009 and rebuild the UTXO set. That's initial block download.

The stages of a first syncHeadersfirstdownload and check all headersBlocksfetch in parallelfrom peersVerifyscripts,amounts, rulesUTXO setbuilt upas you goSyncedfollows newblocks live
The stages of a first sync

What takes time

  • Disk speed and memory: the node constantly reads and updates the UTXO set. More database cache (the dbcache setting) helps a lot.
  • CPU: checking signatures.
  • Bandwidth: hundreds of GB to download.

A fast machine can finish within a day; a slow one with a hard drive can take much longer.

assumevalid

By default, Bitcoin Core skips signature checks for blocks buried under a known block hash shipped with the release. Everything else (amounts, proof of work, UTXO rules) is still fully checked, and the setting can be turned off to verify every signature. This speeds up IBD without trusting anyone for the money supply.

Using a node during IBD

Until it's synced, a node's view of recent blocks, fees and the mempool isn't current.

EXAMPLE

How MyBitcoinExplorer handled its own IBD

While our node was syncing, MyBitcoinExplorer labelled heights as "verified" and withheld fee estimates rather than showing stale data. Sync finished in October 2026; you can check the node's state any time on our status page.

Speed-up tips

  • Use an SSD, not a hard drive. This is the single biggest factor.
  • Raise dbcache (for example 4,000 MB or more) if you have spare memory.
  • Keep the computer awake and on a stable connection.
  • Avoid running heavy tasks on the same machine during sync.

How long will it take?

On a modern desktop with an SSD, often under a day. On a small single-board computer, several days. Progress isn't linear: recent blocks are much fuller than early ones, so the last 20% takes far longer than the first.

Share this guide
Share on X ↗

Key takeaways

  • IBD downloads and verifies every block since 2009.
  • Disk speed, memory cache and CPU set the pace.
  • assumevalid skips old signature checks but still verifies all other rules.

Common questions

Can I use my wallet during IBD?

You can receive, but balances and confirmations aren't reliable until the node has synced.

Can I skip IBD?

Only by trusting someone else's data. Bitcoin Core has an optional 'assumeutxo' snapshot that still verifies history in the background.

Can I stop and resume the sync?

Yes. Bitcoin Core saves progress and continues where it left off.

Why is the end of the sync so slow?

Recent blocks are full and contain many more transactions than early ones.