Full node
Archival validating node
Validates the chain and keeps historical block data after validation.
Useful when you need old blocks, indexes or broader peer serving.
Run a validating Bitcoin node
Your node, from first decision to daily operation.
There is more than one type of Bitcoin node you can run. Compare archival and pruned validation, desktop and dedicated operation, managed platforms and optional Lightning or mining connections before building the setup that fits you.
One connected path
Seven stages, with a clear result at each step
Start at stage one if this is your first node. Returning operators can open any stage directly without resetting progress.
- 01
Current stage
Choose setup
Separate node mode, hardware and software before choosing a product.
Expected result: A setup route that matches your goal and confidence.
- 02
Upcoming
Check hardware
Check the CPU, memory, SSD, internet, Ethernet, power and cooling.
Expected result: Hardware that can remain reliable during initial sync.
- 03
Upcoming
Install
Download from the official project, verify it and select storage settings.
Expected result: Node software installed from a source you verified.
- 04
Upcoming
Synchronise
Let the node obtain and independently validate Bitcoin's history.
Expected result: A recent chain tip, active peers and initial sync complete.
- 05
Upcoming
Maintain
Use safe shutdowns, monitor storage and apply deliberate updates.
Expected result: A stable node with a simple recurring maintenance routine.
- 06
Upcoming
Improve privacy
Connect a wallet locally and secure RPC, remote access and peer traffic.
Expected result: Your wallet asks your node instead of a public blockchain server.
- 07
Upcoming
Troubleshoot
Diagnose startup, sync, peer, disk and wallet issues with reversible checks.
Expected result: A recovery path that preserves keys, configuration and evidence.
Interactive setup environment
Build your node before buying anything
Change the goal, hardware, storage and interface. The live stack updates into a practical starting plan; it never creates keys, opens ports or connects to a real node.
One network, several node setups
There is more than one kind of node you can run
Start with validation: a full node can retain the complete block history or operate in pruned mode. Then choose how it runs—on a desktop, a dedicated machine or a managed platform—and whether to add Lightning, mining support or a test network.
These labels can overlap. One machine could be a dedicated, pruned Bitcoin Core node that also supports a separate Lightning service.
A light or SPV wallet can verify limited evidence, but it does not independently validate every consensus rule like a full node.
Full node
Pruned validating node
Validates from genesis, then removes eligible old block files to limit storage.
It still verifies Bitcoin; it simply retains less historical data.
Operating style
Desktop node
Runs directly on a Windows, macOS or Linux computer with a graphical interface.
A low-cost place to learn before purchasing dedicated hardware.
Operating style
Headless dedicated node
Runs continuously on a mini PC, server or supported single-board computer.
Better for an always-on wallet backend, but requires routine maintenance.
Platform
Managed node platform
Uses a local dashboard to manage Bitcoin and optional related services.
Convenient, with more software layers than a direct Bitcoin Core install.
Additional service
Bitcoin + Lightning node
Runs a Bitcoin validating node beneath a separate Lightning implementation.
Lightning adds channel liquidity, backups and operational responsibility.
Specialised use
Mining-connected node
Supplies independently validated block templates and rules to mining equipment.
An ASIC is not itself a full node; validation and hashing are different jobs.
Testing
Signet or testnet node
Uses a Bitcoin test network to practise configuration and development.
Test coins have no monetary value and must stay separate from mainnet funds.
Software and platforms
Six practical routes, compared without rankings
The choice changes setup and management, not the need to validate Bitcoin. Confirm current hardware support and installation steps with the project before committing a device.
ProjectTypeGood starting fitInterfaceSource
Bitcoin Core
Direct node software
A focused Windows, macOS or Linux node with direct control.
Graphical or command line
OfficialBitcoin Knots
Direct node software
Operators who deliberately want additional policy controls.
Graphical or command line
OfficialUmbrel
Managed node platform
A guided local dashboard on supported hardware or documented DIY setups.
Browser dashboard
OfficialStart9
Managed private server
An always-on server with guided service management.
Browser dashboard
OfficialRaspiBlitz
DIY Bitcoin + Lightning
A hands-on Raspberry Pi build with optional Lightning.
Guided terminal menus
OfficialmyNode
Managed node platform
A browser-managed DIY or pre-built Bitcoin setup.
Browser dashboard
Official21Relay does not rank these projects and receives no compensation for listing them.
First-node checklist
A safe installation path
Each action below links to a fuller guide. The order keeps buying decisions, software verification and security boundaries understandable.
- 1
Define the job
Decide whether the node will verify a wallet, stay online continuously, support Lightning or act as a learning system.
Build a setup - 2
Confirm hardware and storage
Choose an SSD with continuing headroom, stable internet, reliable power and enough cooling for sustained validation.
Check hardware - 3
Download from the official project
Avoid advertisements, mirrors and unsolicited links. Use the current release rather than a version copied into an old guide.
Choose an install guide - 4
Verify before installing
Check the published file hash and signature instructions. Stop if the filename, checksum or source does not match.
Review verification - 5
Choose archival or pruned storage
Both validate the chain. Pruning changes retained history and can limit historical indexes or serving old blocks.
Estimate storage - 6
Synchronise without shortcuts
Keep the device awake and safely powered while it downloads and validates blocks from peers. Pause only with a normal shutdown.
Understand sync - 7
Verify the result
Check that the chain tip is recent, peers are connected, warnings are clear and initial block download has completed.
See health checks - 8
Connect, protect and maintain
Connect a compatible wallet over a trusted path, keep RPC private and adopt weekly, monthly and update-time checks.
Set a routine
Tips that prevent common failures
Keep the first build boring and dependable
Performance
- Use an SSD rather than a hard disk for chainstate-heavy work.
- Prefer Ethernet for an always-on node and prevent sleep during sync.
- Leave free storage beyond the current chain size for growth, logs and updates.
- Expect initial sync time to vary widely with CPU, SSD and connection quality.
Security
- Download only from the official project and follow its current verification steps.
- Never expose RPC credentials or unrestricted management interfaces publicly.
- Inbound peer port 8333 is optional; it is not required for outbound validation.
- Use a normal shutdown. Do not unplug storage while the node is writing.
Operations
- Back up private keys, descriptors, labels and deliberate configuration changes.
- Block data and chainstate can be downloaded and rebuilt; private keys cannot.
- Check recent block time, peers, warnings, storage and temperature routinely.
- Add Tor, remote access or Lightning only after the base node is healthy.
Primary documentation
Check the live source before installation
Versions, hardware support and security procedures change. These links lead to the project documentation used to review this journey.