Full node setup guide
Build a Bitcoin Node
A practical guide to choosing hardware, installing Bitcoin Core, and understanding what a full node does.
Bitcoin Core is the reference full node software. It validates Bitcoin rules locally and helps users independently verify the chain they accept.
Basics
What a Bitcoin node does
A Bitcoin full node verifies the rules of Bitcoin on your own machine. It is not a wallet by itself, and it does not need private keys to validate blocks or transactions.
Hardware
Hardware overview
Exact requirements change over time, so treat this as practical orientation rather than permanent minimums. Check Bitcoin Core's current requirements before buying new hardware.
Small computer
Common choices include a Raspberry Pi 5, a mini PC, a spare desktop, or a spare laptop. A machine you already own can be a good first learning path.
SSD storage
SSD storage is strongly preferred. A 1TB SSD is commonly used as a minimum starting point, while 2TB is more comfortable for future growth.
RAM and CPU
More RAM and a faster processor can make setup feel smoother, but modest systems can work. Check Bitcoin Core's current requirements before buying anything.
Network
Reliable home internet matters more than peak speed. Ethernet is usually more stable than Wi-Fi for an always-on node.
Power
Use a stable power supply, especially for a Raspberry Pi. Sudden power loss can interrupt sync and may damage cheap storage.
Cooling
Small always-on computers need airflow. A case with simple cooling can help keep performance steady during Initial Block Download.
Setup paths
Choose a setup path
Start with the simplest path that matches your comfort level. Desktop is easiest, a dedicated machine is better for always-on use, and a headless setup is flexible but more technical.
Easiest: desktop or laptop
Install Bitcoin Core on an existing computer.
- Good for learning the basics with the least extra hardware.
- Works well if you can leave the computer online while it syncs.
- May be less ideal as a permanent always-on node.
Dedicated home node
Use a mini PC or Raspberry Pi with SSD storage.
- Better fit for always-on use than a daily laptop.
- Mini PCs are often simpler for beginners.
- Raspberry Pi builds are popular but more hands-on around storage, power, and cooling.
Advanced: headless Linux/server
Run Bitcoin Core on a machine you administer remotely.
- Flexible for command-line users who want more control.
- Requires comfort with Linux services, firewalls, logs, and updates.
- More control also means more responsibility.
Basic steps
From hardware to first check
This is the short version of the setup flow. Follow the official Bitcoin Core instructions for the operating system you choose.
- 1Choose hardware that matches your comfort level and whether the node should be always on.
- 2Install an operating system if the machine does not already have one.
- 3Download Bitcoin Core from the official Bitcoin.org page.
- 4Start Bitcoin Core and choose a data directory on the SSD.
- 5Let Initial Block Download complete or make steady progress.
- 6Decide whether you want to accept inbound clearnet connections.
- 7Optionally forward TCP port 8333 and allow it through your firewall.
- 8Use Check My Node to test whether the node appears reachable from this project's server.
Initial sync
Storage and Initial Block Download
During Initial Block Download, Bitcoin Core downloads blocks and verifies them locally. This can take a long time, especially on slow storage or older hardware.
- Initial Block Download can take a long time because Bitcoin Core verifies the chain locally.
- SSD storage is strongly preferred over microSD cards or slow external drives.
- Keep extra free space for future chain growth, operating system updates, logs, and temporary files.
- Pruned mode can reduce storage needs, but it is different from keeping the full chain history available locally.
- Avoid making plans around one precise blockchain size; check current Bitcoin Core requirements before buying storage.
Reachability
Port 8333 and inbound peers
Reachability is about whether other peers can connect to your node from the public internet. It is useful, but optional.
- Bitcoin mainnet uses port 8333 by default for peer connections.
- A full node can run without inbound reachability and still validate Bitcoin locally.
- Public reachability usually requires router port forwarding and firewall rules.
- Some ISPs, routers, or carrier-grade NAT setups prevent inbound connections.
- Only expose the Bitcoin node port you intend to expose; do not open unrelated services.
Hardware links
Recommended hardware categories
You do not need a special branded node device. These links are generic searches for common categories, not specific product endorsements. Running a Bitcoin node does not require buying through these links.
Affiliate disclosure
As an Amazon Associate I earn from qualifying purchases. Some hardware links are paid affiliate links. Running a Bitcoin node does not require buying through these links.
Choosing hardware
Raspberry Pi vs mini PC
Raspberry Pi builds are popular, but a mini PC can be simpler for a beginner who wants a dedicated always-on machine.
| Topic | Raspberry Pi | Mini PC |
|---|---|---|
| Setup feel | More hands-on, especially around imaging, storage, and cooling. | Usually closer to setting up a normal small computer. |
| Power use | Very low power draw. | Still modest, but usually higher than a Raspberry Pi. |
| Storage | Use a reliable external SSD, not only a microSD card. | Internal or external SSD options are often easier to manage. |
| Good fit | Good for tinkerers who want a small low-power project. | Good for beginners who want a dedicated always-on node. |
Safety
Privacy and safety notes
A node is infrastructure software. Treat the machine and your network settings with the same care you would give any always-on internet-connected service.
- Do not publish personal IP details unnecessarily.
- Running a public node can reveal your IP address as a Bitcoin node.
- Use official downloads and verify signatures or checksums when possible.
- Never paste wallet seeds, private keys, or signing material into websites.
- Bitcoin Node Atlas does not need wallet keys to check reachability.
- This guide is educational and is not financial advice.
Troubleshooting
Common troubleshooting
If your node is not reachable, work through the basics before changing many settings at once.
- Bitcoin Core is running and fully started.
- Initial Block Download may take time before the node is useful.
- Port 8333 may need router forwarding if you want inbound clearnet reachability.
- A local firewall may block inbound connections.
- Your ISP or router may not allow inbound connections.
- Tor nodes may not appear in the regular clearnet checker.
- Reachability checks are from our crawler's vantage point and may not be perfect.
FAQ
Common questions
Short answers for common beginner questions before you choose a setup path.
Do I need special hardware?
No. Many people start on an existing desktop or laptop. A dedicated mini PC or Raspberry Pi can be useful if you want an always-on node, but it is not required for learning.
Do I need to keep the node online all the time?
No. A node that is online more often is more useful to you and to peers, but it can still validate locally when you run it. If it is offline for a while, it needs to catch up when restarted.
Do I need to open port 8333?
No. Opening port 8333 is only needed if you want inbound clearnet peers to reach your node. Public reachability is optional.
Why does my node not show on the map?
The map only shows observed nodes with approximate IP geolocation from this crawler's vantage point. Private nodes, unreachable nodes, Tor/onion nodes, and nodes without GeoIP data may not appear.
Is Bitcoin Node Atlas a complete list of all nodes?
No. It is an observed view from one conservative crawler vantage point, not a complete census of every Bitcoin node.
Does running a node earn bitcoin?
No. Running a full node by itself does not earn bitcoin. It helps you validate Bitcoin rules locally and participate in the peer-to-peer network.