Part of the Build a Bitcoin Node pathway. Use the guide library to follow another setup path.
Choose and verify the official release
Download Bitcoin Core for your operating system and CPU architecture from the official project site. Follow its current signature and checksum verification instructions before installing. Avoid treating a search advertisement or a third-party download mirror as proof of authenticity.
Keep operating system updates and backups in place. Node data and wallet secrets are different: the blockchain can be downloaded again, but wallet recovery depends on the wallet's own backup and recovery process. You do not need to create or fund a wallet to run a node.
Desktop path
Launch the graphical application and select a data directory on reliable storage with room to grow. Decide whether pruning fits your use before downloading. Keep the computer awake during the hours you want it to sync; sleep stops progress and peer service.
- Install the verified package for your operating system.
- Choose a persistent data directory and retention setting.
- Allow outbound network access if your firewall prompts.
- Leave synchronization running and inspect progress in the interface.
- After sync, decide whether you want inbound peers before changing router rules.
Linux server path
Use a regular dedicated account for the node and a persistent data directory that account owns. Launch bitcoind with settings appropriate to the installed release. Use bitcoin-cli locally under the intended account to inspect getblockchaininfo and getnetworkinfo. Never expose the RPC interface to the public internet as a way to make the P2P node reachable.
A service manager can handle boot-time startup and graceful shutdown, but validate the data path, user permissions and log destination first. Keep administrative access protected and monitor disk space. Server administration offers more control and also makes you responsible for updates, firewall rules, process health and recovery.
Check progress before troubleshooting reachability
In the desktop interface, examine sync progress and peer connections. On a server, getblockchaininfo reports fields such as blocks, headers, verificationprogress and initialblockdownload. Compare observations over time instead of assuming a percentage must move at a constant speed.
If progress stops, check storage space, connection count, operating system logs and whether the machine is sleeping or throttling. Avoid deleting the data directory as a first response; identify the failure before starting another large download.
After installation
Inbound public service is optional. If you enable it, use the P2P port and restrict the firewall rule to the intended service. Bitcoin mainnet normally uses TCP 8333. Keep remote administration and RPC separate.
Use Atlas's checker only for an address you intend to expose publicly. A successful handshake is a point-in-time result from one server; an unsuccessful result does not prove your node cannot validate or connect outbound.
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.