Part of the Build a Bitcoin Node pathway. Use the guide library to follow another setup path.
Start with the computer you already have
A spare desktop or laptop can be a useful place to learn Bitcoin Core. The practical question is whether it can validate steadily, store its data reliably and stay connected for the hours you intend to run it. You do not have to buy a dedicated appliance or leave a node running every hour of the day.
For a dedicated machine, evaluate the complete setup: storage, power supply, cooling, operating system support and a wired network connection. A headline CPU specification does not capture slow storage, thermal throttling or unreliable USB adapters.
Choose archival or pruned storage first
The blockchain grows, so an old quoted chain size is a poor purchasing target. Check current Bitcoin Core guidance and allow headroom for growth, chainstate, indexes, downloads and the operating system. A 1 TB or 2 TB SSD is a capacity option to evaluate, not a promise that every configuration will fit indefinitely.
Pruning can retain a smaller set of block files while still validating. It does not cap the entire data directory or eliminate initial download bandwidth. Archival retention is useful when you want to serve old blocks or use software that expects them. Decide on your wallet and indexing needs before choosing a pruning target.
CPU, memory, cooling and power
Initial block download stresses CPU and random storage access more than quiet steady-state operation. An SSD generally makes a more practical primary data drive than relying on a microSD card for the whole workload. Keep the operating system and SSD supported and monitor free space.
More cache can help some systems, but do not allocate all memory to Bitcoin Core. Leave room for the operating system and other applications. On small boards, cooling and a properly specified power supply can matter as much as the processor. Shut down cleanly before disconnecting storage or power.
Budget for download and upload separately
Initial synchronization downloads substantial historical data even in ordinary pruning mode. After sync, new blocks and transaction relay continue to use bandwidth. Serving inbound peers can add significant upload traffic. Check your ISP's data cap, upload capacity and service terms before enabling public reachability.
Bitcoin Core has network and upload settings, but an upload target is not a universal hard cap on every byte of traffic. Monitor the machine and router, consult your installed version's help, and adjust conservatively. A slow sync does not necessarily mean the internet connection is the bottleneck.
Make a purchase checklist
Compare a Raspberry Pi with all required accessories against a mini PC with an SSD included. Account for drive endurance, cooling noise, electricity and replacement parts. The dedicated guides explain the different setup responsibilities.
- Choose archival or pruned retention based on your actual use.
- Confirm OS and CPU architecture support for your chosen software.
- Allow storage and memory headroom instead of sizing to an old minimum.
- Use reliable power, cooling and Ethernet where practical.
- Check bandwidth allowances and decide whether inbound service is appropriate.
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.