Headers first
The node learns block headers, then downloads and validates block contents and transactions.
Run Your Node
Stage 4 of 7
Synchronise and verify the chain
Initial block download is verification work, not simply copying a database. Let the node finish before relying on it for wallet verification.
What to expect
CPU and SSD activity
Historical signature checks and chainstate updates can keep the processor and SSD busy. Speed varies substantially by hardware.
Pruning happens after validation
A pruned node still validates old blocks before deleting eligible block and undo files.
Healthy sync checklist
- Block and header counts continue moving
- Verification progress increases over time
- The latest block time becomes more recent
- Peer connections remain available
- Free disk space stays above your planned reserve
- No persistent warning remains unexplained
Technical checks
- 1
Check blockchain state
Run bitcoin-cli getblockchaininfo or use the GUI Information window.
Expected result: blocks approaches headers; verificationprogress approaches 1; initialblockdownload becomes false.
- 2
Check networking
Run bitcoin-cli getnetworkinfo or view peer information in the GUI.
Expected result: networkactive is true and connections is above zero.
- 3
Wait for completion
Keep the node open and prevent sleep. You can pause by shutting down normally and resume later.
Warning: Do not unplug its data drive or force power off during active database writes.
Official sources
Stage progress
Mark this stage complete when you are ready to continue.