Part of the Build a Bitcoin Node pathway. Use the guide library to follow another setup path.
Synchronization is more than a download
Bitcoin Core must obtain chain data and perform validation work. Network throughput is only one constraint: CPU, cache, storage latency and available peers affect progress. Historical workload is uneven, so a progress bar need not advance at a constant rate.
There is no universal completion time. Compare the node's own progress over an interval long enough to see movement and check resource usage before deciding it is stuck. Another person's benchmark on different hardware is not a reliable deadline.
Read progress in context
The desktop interface shows synchronization status. Local getblockchaininfo output includes blocks, headers, verificationprogress and initialblockdownload. Headers alone are not proof that all corresponding blocks have been validated.
Observe whether validated blocks increase and whether peers remain connected. A low network download rate can occur while the machine is busy validating already received data. Also check temperature and storage activity; sustained thermal throttling or a slow external drive may dominate performance.
Pruning does not skip initial validation
Ordinary pruning discards older block files after they have been processed. It reduces retained storage, not the need to obtain and validate history during ordinary initial synchronization. Keep space for chainstate and indexes beyond the configured pruning target.
Do not copy an untrusted data directory as a shortcut or assume a fast sync proves the source is trustworthy. Follow the official documentation for any supported initialization features in your installed release and understand their trust assumptions.
A practical stalled-sync checklist
Start with observable resource and connectivity problems before changing application settings. Record errors and the block progress over time so you can distinguish slow progress from repeated failure.
- Confirm the computer is awake and Bitcoin Core is still running.
- Check free disk space, drive connections and operating system errors.
- Confirm outbound peers and that the internet connection is not capped or interrupted.
- Inspect CPU load, temperature and memory pressure.
- Read the application log for a specific error before attempting repairs.
- After a clean restart, compare progress again; avoid repeated forced shutdowns.
After synchronization
Keep the node connected according to your intended uptime and monitor growth. Accepting inbound peers is optional and requires its own network configuration. Atlas's reachability check tests a handshake; it is not a definitive test that your node is fully synchronized.
Official references
Check settings against your installed release. The Bitcoin full node guide explains operation and connectivity; Bitcoin Core downloads includes verification instructions. For sync diagnostics, consult the versioned getblockchaininfo reference and your release's built-in help.
Ready to test inbound P2P access? Check whether your Bitcoin node is reachable. To interpret what Atlas sees, explore observed Bitcoin nodes and our methodology.