A full node is a computer running Bitcoin software that downloads every block and checks every transaction against the network's consensus rules, without trusting anyone else's word. The distinction that matters is verifying versus storing. A pruned node deletes old blocks but still validates the entire history, so it is as much a full node as one keeping more than 600 GB on disk. A full node does not mine, and it will not earn you money.
TL;DR:
- A full node independently checks every block and transaction against Bitcoin's rules. "Full" refers to validation, not to how much it stores.
- A pruned node validates the same history as an archival node but can keep under 15 GB on disk instead of more than 600 GB.
- Plan for 4 GB of RAM as the practical minimum for Bitcoin Core alone and 8 GB if a payment server runs on the same machine. Storage speed matters more than RAM for the initial sync.
- Running a node pays nothing, and it is not mining. Its value is that nobody else gets to tell you whether you were paid.
- A self-hosted payment server needs a full node behind it. The real decision is whether you maintain that node or pay someone to.
Table of Contents
- What a Full Node Actually Does, and Why "Full" Means Verify, Not Store
- Full Node, Pruned Node, Light Wallet, Miner: The Types of Nodes Compared
- Bitcoin Full Node Size: Archival vs. Pruned, and Why the Big Number Is Optional
- Bitcoin Node Hardware: How Much RAM, Disk and Bandwidth You Really Need
- Does a Bitcoin Node Make Money? Profit, Mining and the Coinbase Question
- Why a Self-Hosted Payment Server Needs Its Own Full Node
- Run It Yourself or Have It Run: The Honest Trade-Off
- Get a Full Node Behind Your Checkout Without Becoming a Sysadmin
- Frequently Asked Questions
- Sources
What a Full Node Actually Does, and Why "Full" Means Verify, Not Store
A Bitcoin full node is software that enforces the network's rules on its own machine. It downloads each block, checks that the proof-of-work is valid, confirms that no coins were spent twice, makes sure no transaction creates bitcoin from nothing, and rejects anything that breaks consensus. It does not ask another server whether a payment is real. It works that out itself.
The purpose of a Bitcoin node is to remove trust from the act of checking. Any wallet that relies on someone else's server is accepting that server's account of the blockchain. A full node accepts only what it has verified. Bitcoin.org's guide to running a full node describes full nodes as the programs that fully validate transactions and blocks. The network as a whole depends on thousands of these machines independently refusing invalid data.
So what is a full node in blockchain terms generally? The idea carries across chains. A full node holds enough state to validate new blocks without outside help and applies the protocol's rules itself. The size and hardware demands differ enormously from one chain to the next. This article is about Bitcoin, where those demands are modest by design.
The word "full" misleads people. It sounds like "stores everything." In practice it means "verifies everything." That difference decides how much disk you need, and it is why many people overspend on hardware they never needed.
Full Node, Pruned Node, Light Wallet, Miner: The Types of Nodes Compared
There are four main types of nodes, and only some of them validate anything. The Bitcoin whitepaper already distinguished full validation from "simplified payment verification" in its eighth section. That split is still the most useful way to sort them.
| Node type | Validates every block? | Stores full history? | Typical disk | Who uses it |
|---|---|---|---|---|
| Archival full node | Yes | Yes | 600+ GB and growing | Explorers, developers, anyone serving old blocks to peers |
| Pruned full node | Yes | No, only recent blocks | Roughly 10–15 GB plus your prune target | Individuals, small merchants, payment servers |
| Light / SPV client | No, checks headers and relies on others for the rest | No | Megabytes | Mobile wallets |
| Mining node | Yes, by running a full node | Usually | Same as archival | Mining pools and solo miners |
Listening vs. non-listening nodes
A listening full node accepts inbound connections on port 8333 and serves blocks to other peers. A non-listening node only connects outward. Both validate identically. Listening helps the network, but it is not required for your own verification. It also costs you upload bandwidth.
What "full node mining" really means
Miners run full nodes so they know which transactions are valid and which chain tip to build on. Running a full node does not mean you are mining, though. Mining requires dedicated ASIC hardware competing for blocks, and a node on a laptop contributes nothing to that race.
Bitcoin Full Node Size: Archival vs. Pruned, and Why the Big Number Is Optional
An archival Bitcoin full node needs more than 600 GB today, and the chain grows by tens of gigabytes a year. Size the drive for that growth: a 2 TB SSD gives an archival node years of headroom, while a 1 TB drive will get uncomfortable sooner than most people expect.
A pruned node still downloads and verifies every block since 2009. It then deletes old block files once they have been checked, keeping the chainstate and a window of recent blocks. The chainstate is the database of every unspent output, and it is the part that actually matters for validation. It is roughly 10 GB on its own, so a pruned node fits comfortably on a modest drive.
550 MiB. That is the smallest prune target Bitcoin Core accepts, and a node pruned that far still verifies every block back to 2009.
The trade-off is real but narrow. A pruned node cannot serve historical blocks to peers. It also cannot rescan a wallet for transactions older than its pruned window. For a merchant whose wallet is created when the store goes live, that limit rarely matters. For someone importing an old wallet with years of history, it matters a great deal.
My recommendation: run archival if you have the disk and want to support the network. Run pruned if you are on a VPS, a small SSD, or a box doing other jobs. Pruning trades storage, not security.
Bitcoin Node Hardware: How Much RAM, Disk and Bandwidth You Really Need

You need about 4 GB of RAM to run Bitcoin Core comfortably. It will start on 2 GB, but anything else on the machine will then fight it for memory. If a payment server, database and wallet indexer share the same box, 8 GB is the sensible floor. The reference software is published at bitcoincore.org. Its default database cache is 450 MiB, so RAM beyond that mostly helps during the initial sync.
The component that matters most is storage speed, not RAM. The initial block download (IBD) means replaying every transaction in history, which produces heavy random reads and writes. On a spinning hard drive, or an SSD attached over a cheap USB adapter, IBD can stretch from hours into a week or more.
| Setup | RAM | Storage | Rough initial sync | Good for |
|---|---|---|---|---|
| Single-board computer kit | 4–8 GB | 1–2 TB external SSD | Several days to a week+ | Hobbyists, home node |
| Mini PC or old desktop | 8–16 GB | 2 TB internal NVMe | About a day | Archival node plus payment server |
| VPS, pruned | 4–8 GB | 80–150 GB SSD | One to two days, CPU-bound | Pruned node behind a store |
Pro Tip: Raise dbcache to several gigabytes for the initial sync only, then drop it back to the default. A large cache sharply reduces disk writes during IBD. Once you are synced, that memory does almost nothing, and on a shared machine you will want it back for your payment stack.
Bandwidth. The first sync downloads the entire chain. After that, a non-listening node uses only a few gigabytes a month. A listening node can upload far more than it downloads. Bitcoin Core's maxuploadtarget setting caps that if your connection is metered.
Bitcoin node kits. Prebuilt kits are convenient, but check two things before buying. Find out whether the SSD is internal or USB-attached. Find out whether the operating system runs from an SD card, since SD cards wear out under constant writes. Both are common weak points.
Does a Bitcoin Node Make Money? Profit, Mining and the Coinbase Question
A Bitcoin node makes no profit. The protocol pays block rewards and fees to miners, not to validators. Running a node costs you electricity, storage and attention, and pays you nothing directly.
Zero. That is what the Bitcoin protocol pays you for running a full node.
The return is indirect but concrete. When someone sends you bitcoin, your own node confirms the payment is valid. You do not rely on a third party that could be wrong, compromised, or simply offline. For anyone receiving payments, that independence is the whole point.
"Coinbase" is a technical term here, separate from any exchange. The coinbase transaction is the first transaction in every block. It is how a miner claims newly issued bitcoin plus fees. Full nodes enforce the rules around it, including that a coinbase output cannot be spent until it is 100 blocks deep. If your bitcoin sits in an exchange account, by contrast, you are trusting that company's node, not running your own.
Public lists of Bitcoin nodes come from crawlers such as Bitnodes, which maps reachable nodes by country and software version. Those lists only count listening nodes. Non-listening nodes, including most nodes running behind payment servers, never show up.
Why a Self-Hosted Payment Server Needs Its Own Full Node
A self-hosted payment server like BTCPay Server watches the blockchain for payments to your addresses. It needs a source of truth to do that, and the source is a full node it controls. The BTCPay Server documentation describes a stack that pairs Bitcoin Core with an indexer that tracks your wallet's addresses. If you want the moving parts explained, our plain breakdown of how BTCPay Server works walks through each one.
The node is what makes the payment yours. Because the server derives addresses from your wallet's public key, coins go straight to you. Because your own node verifies the payment, no processor sits in the middle deciding whether it counts. That arrangement also removes the reason a processor would take a cut. Our breakdown of percentage fees on bitcoin payments shows what that cut adds up to at real order volumes.
A pruned node is enough for this job. The payment server only needs to see new blocks from the moment your store starts watching addresses. It does not need fifteen years of historical blocks on disk.
Pro Tip: Connect your store's wallet before or right after your pruned node finishes syncing. Do not do it months later. A pruned node cannot rescan blocks it has already deleted, so any payments to that wallet from before the prune window will not appear.
Run It Yourself or Have It Run: The Honest Trade-Off

Running your own node is not hard, but it never stops. The initial sync takes a weekend. After that come updates, disk monitoring, restarts after power cuts, and catching up when the node falls behind. A node that silently stops syncing on a Friday night means invoices that never confirm until Monday.
Run it yourself if you already manage servers, enjoy it, and have a machine with fast storage and steady uptime. You get the strongest form of sovereignty and pay only for hardware and power.
Have it run for you if your business is selling things, not maintaining Linux boxes. The cost of a missed payment or a broken checkout during a sale outweighs any hosting fee. For a store doing meaningful volume, a flat monthly fee usually beats a percentage well before the end of the first month.
I would pick self-hosting for a hobbyist and a managed node for almost any merchant. The validation is the same either way. What changes is who gets paged when it stops working.
Get a Full Node Behind Your Checkout Without Becoming a Sysadmin

Myntli runs the full node and BTCPay Server for you. We handle installation, monitoring, updates and sync maintenance, so the failure points described above are ours to watch, not yours. The hosted option puts your store on our node for $29 a month. If you would rather own the hardware, we install a full BTCPay Server node on your own server for a one-off $449. Either way, customers pay straight into your own wallet. We take no percentage, hold no custody of your funds, and require no KYC on your store.
We also wire it into the shop you already use, including WooCommerce, Shopify, Ghost, Magento, PrestaShop and others, and help you set up a self-custody wallet if you don't have one. One honest limit: on the hosted plan you rely on our node's view of the chain, not one under your own roof. If independent verification is the point for you, choose the $449 install on your own server, and check its disk and RAM against the table above before you buy hardware.
Frequently Asked Questions
What is the purpose of a Bitcoin node?
A Bitcoin node independently checks every block and transaction against the network's rules and relays valid data to peers. Its purpose is to let you confirm payments yourself instead of trusting a third party's server. The network stays honest because thousands of nodes reject invalid blocks on their own.
How much RAM do you need to run a Bitcoin node?
Bitcoin Core will start on 2 GB of RAM, but 4 GB is the practical minimum for stable use. If you also run a payment server, database and wallet indexer on the same machine, plan for 8 GB. Fast SSD storage matters more than extra RAM for how quickly the node syncs.
Is a pruned node a real full node?
Yes. A pruned node downloads and verifies every block in Bitcoin's history, then deletes old block files to save space. It validates exactly as strictly as an archival node. It just cannot serve old blocks to peers or rescan for very old wallet transactions.
How big is a Bitcoin full node?
An archival Bitcoin full node needs more than 600 GB of disk, and the chain grows by tens of gigabytes a year, so a 2 TB SSD is a sensible buy. A pruned node can run in roughly 10–15 GB plus whatever prune target you choose.
Can you make money running a Bitcoin full node?
No. The Bitcoin protocol pays block rewards and fees to miners, not to nodes that only validate. The benefit of running a node is independence: you verify your own payments rather than trusting someone else's.
Does running a full node mean I am mining bitcoin?
No. Miners run full nodes, but a full node alone does not mine. Mining requires specialized ASIC hardware competing to produce blocks, which is a separate and far more expensive operation.
Sources
- Bitcoin: A Peer-to-Peer Electronic Cash System | Satoshi Nakamoto / Bitcoin.org
- Running A Full Node | Bitcoin.org
- Bitcoin Core | Bitcoin Core project
- Bitnodes: Global Bitcoin Nodes Distribution | Bitnodes
- BTCPay Server Documentation | BTCPay Server Foundation
