Running a full node

The job is a background process, not a hobby. A second-hand mini PC, a 2 TB drive and a day or two of patience produce a machine that verifies your own payments, and pruning cuts the storage requirement to 550 MiB if disk is the obstacle. It earns nothing at all, which is the point: nobody can pay you to lie to yourself.

How it works

Running a full node breaks into four decisions, and only one of them costs money.

The first is software. Bitcoin Core is the default and the implementation everything else is tested against. Bitcoin Knots is the same validation with tighter relay defaults. If a command line holds no appeal, Umbrel, Start9, RaspiBlitz and myNode wrap Bitcoin Core in a web interface and handle the plumbing, at the cost of trusting whoever assembled the package.

The second is hardware, where the binding constraint is disk rather than processor. The full archive passed 759 GB in August 2026, so a 1 TB drive is already uncomfortable and 2 TB is the sensible purchase. A solid state drive matters far more than a fast processor, because the slow part of syncing is not verifying signatures but reading and rewriting the unspent output database millions of times over. Two gigabytes of memory is enough; four makes the sync noticeably quicker.

The third is how much history to keep. An archival node stores every block since January 2009 and can serve them to others. A pruned node deletes raw block files once it has validated them, and prune=550 is the minimum setting, 550 MiB of block storage. Pruning weakens nothing: the same rules run in the same order over the same data. What you give up is serving old blocks to peers, rescanning a wallet from a distant birth date, and running a transaction index.

The fourth is how you reach the tip. Left alone, Bitcoin Core fetches headers, then bodies in parallel, then validates everything, and that takes hours on a good machine or a couple of days on a Raspberry Pi with an external drive. Raising dbcache to a few thousand megabytes gives the output set room in memory and cuts the time substantially. Since version 26.0 there is a shortcut: loadtxoutset imports a snapshot of the unspent output set, checks its hash against a value compiled into the release, and produces a usable node in minutes while the full history validates in the background behind it.

After that the node runs unattended. Outbound connections need no configuration at all. Accepting inbound peers means opening port 8333 or letting Bitcoin Core publish a Tor hidden service, which it arranges by itself when Tor is installed.

Why this matters when you buy bitcoin

A node answers the one question an exchange cannot answer for you: whether the coins actually arrived.

Our 231 country guides cover who may legally sell to you, and our exchange reviews cover what each platform charges to get coins out. Neither can tell you what happened on the chain. When a platform marks a withdrawal as sent, you are reading a row in its database. A node reading the chain is the independent check, and it is the same check that turns a claimed proof of reserves from a press release into something you can inspect.

Privacy is the second reason, and the one people underrate. A wallet that queries a public server or a block explorer discloses the addresses it watches, which amounts to a running inventory of your holdings tied to an IP address. Point that same wallet at your own node and the disclosure stops. This is a privacy measure and nothing more: it does not change what is legal where you live, and the countries our guides mark as restricted stay restricted whether or not you run one.

There is a fee argument too. Every wallet's suggested fee comes from somebody's mempool, and in a busy week those estimates diverge sharply. Your own node keeps its own mempool and its own estimator, so you can decide what to pay from your own data rather than from a platform's interest in seeing the transaction clear quickly.

What a first sync actually costs

Adding up one real installation makes the decision concrete rather than ideological.

Hardware is a used mini PC and a 2 TB NVMe drive. Bandwidth is the download of an archive past 759 GB, which matters on a metered connection, and if you accept inbound peers you will upload some multiple of that over a year serving history to strangers. Time is hours to a couple of days, or minutes if you load a UTXO snapshot and let the history catch up behind you. Electricity is the smallest line: a machine drawing ten watts continuously uses roughly 88 kilowatt hours a year, which at twenty cents a unit is under twenty dollars.

The revenue is zero. Not small, zero. A validating node collects no subsidy, no fee and no yield, and there is no mechanism by which it could. Any product marketed as a node that pays a return is selling something else, usually a staking scheme wearing bitcoin's vocabulary, and it belongs in the same category as the schemes catalogued in our scam guide.

Running a full node vs a hardware wallet

A full node and a hardware wallet do opposite halves of one job and are frequently bought as substitutes. A hardware wallet holds a private key and signs what you approve; it carries no copy of the chain and cannot tell you whether a payment arrived or whether the coins you think you hold exist. A full node holds the entire chain and no keys whatsoever. Together they are complete: the node tells your wallet software what you own, and the signer authorises the spend. Buying one under the impression that it covers the other leaves a real gap.

Running a full node vs a Lightning routing node

A bitcoin full node and a Lightning routing node are both called nodes, and only one of them can pay you. A Lightning routing node keeps payment channels open, forwards other people's payments and may collect small routing fees, with capital locked up and an uptime requirement attached. A bitcoin full node validates blocks, forwards transactions and earns nothing. Nearly every Lightning node needs a bitcoin node underneath it to watch the chain on its behalf. The distinction matters because when somebody advertises income from running a node, they mean the Lightning kind, or they mean nothing at all.