Live ¡ Bitcoin node

What a Bitcoin node does, and how to run one

By the CloudMineCrypto teamUpdated 8 min read

The short answer

A Bitcoin node is a computer that keeps its own copy of the blockchain and checks every transaction and block against the rules. Nobody can pay you with fake coins or break the 21 million cap without your node noticing. A full node needs about 780 GB of disk today, or around 7 GB if you prune old blocks. Miners and pools use one to build the blocks they mine.

Key takeaways

  • A node verifies. A miner proposes blocks. Mining needs a node; a node doesn’t need mining.
  • Full and pruned nodes check exactly the same rules. Pruning only deletes old blocks afterwards.
  • Running a node earns nothing. People run one to trust nobody with their own payments.
  • A modest computer and an SSD will do. The first sync is the slow part.

What your node does · one transaction’s trip

Live network data

Step 1 of 6

A transaction arrives from a peer

Someone presses send. Their wallet hands the transaction to a node, and it spreads peer to peer. Yours hears about it from one of its connections within seconds.

By the rules

11

outbound peers Bitcoin Core keeps by default

  • 8 full-relay peers
  • 2 block-relay-only peers
  • more inbound if you open port 8333

Mempool and block figures are live from public block explorers, refreshed every few minutes. Defaults are Bitcoin Core’s.

What is a Bitcoin node?

Definition ¡ Full node

A program that downloads every Bitcoin block and transaction, checks each one against the consensus rules, and relays the valid ones to other nodes. It accepts nothing on trust.

There’s no central server in Bitcoin. Nodes all over the world each hold the same ledger and enforce the same rules, and they talk to each other directly. Bitcoin Core is the software most of them run.

#972,082

blocks in the chain

live

776 GB

of block data

blockchain.com, 2026-10-14

166.1M

unspent outputs (UTXO set)

what a node checks spends against

37,925

transactions waiting

live, mempool.space

The point is independence. A wallet connected to your own node doesn’t ask anyone whether a payment is real. It checks. That also keeps your addresses private, because you’re not telling someone else’s server which ones are yours.

What does a Bitcoin node check?

Every rule, on every block, from the first one in 2009. A block that breaks one is rejected, however much work went into it. That’s what gives miners a reason to play fair.

Work

The block hash is below the target, so real proof of work went into it.

Supply

The miner pays itself no more than 3.125 BTC plus fees. This is how the 21 million cap holds.

No double spends

Every coin spent exists and hasn’t been spent before.

Signatures

Only the owner of a coin could have signed its spend.

Size

The block fits in 4,000,000 weight units.

Chain

It builds on a block your node already accepted, with a sane timestamp.

The work check is the cheap one: a single hash compared with the target. Proof of work shows why finding that hash is hard and checking it is instant. The reward check is why a miner can claim the block reward and fees but never a satoshi more.

Full node vs pruned node vs light client

All three talk to the Bitcoin network. The difference is how much they check for themselves and how much they keep.

Full node (archival)

776 GB

Checks everything, keeps everything

Every block since 2009. Can serve old blocks to new nodes.

Verifies: Every rule

Pruned full node

about 7 GB

Checks everything, keeps the recent part

Downloads and checks every block, then deletes old ones. Minimum 550 MiB of blocks kept.

Verifies: Every rule

Light client (SPV)

78 MB

Trusts full nodes for the rest

Mostly block headers, 80 bytes each: 972,082 of them. Many phone wallets use a light client or a server someone else runs.

Verifies: Proof of work only

Bars on a log scale, so the light client stays visible. Pruned size from bitcoin.org’s node guide; the other two are computed from live chain data.

A pruned node is still a full node in every way that matters for your security. It just can’t hand old blocks to a new node that’s syncing, and a few features that need the whole history, like a full transaction index, are off.

A light client, often called SPV after section 8 of the whitepaper, only checks that blocks carry enough work. It relies on full nodes to tell it about its own transactions. That’s fine for a phone, and it’s why full nodes matter: someone has to answer.

Why do miners and pools need a node?

To know what to mine. A miner can’t hash an empty idea; it needs a block template: the previous block’s hash, the transactions to include and the coinbase that pays the reward. Only a node that’s up to date can build a valid one.

StepWho does itHow
Pick transactionsThe nodeThe best fee rates from its mempool, up to 4,000,000 weight units
Build the templateThe nodegetblocktemplate hands it to mining software
Hash itThe minersBillions of tries a second across the pool
Broadcast the winnerThe nodeSends the block to its peers, who check it

Under Stratum V1, the protocol most pools still use, the pool’s node does all of this and miners just hash. Stratum V2 adds job declaration, so a miner can build templates with its own node and still be paid by the pool:

Stratum V1 (most pools today)

Pool’s nodetemplatePooljobYour miner

The pool’s node picks the transactions. Miners hash whatever job they’re sent.

Stratum V2 with job declaration

Your nodetemplateYour minersharesPool

The miner’s own node picks the transactions and tells the pool. The pool still counts shares and pays out.

That matters because whoever builds the template decides which transactions get in. See which pools find most blocks right now in the biggest Bitcoin mining pools, and how they pay miners in mining pools explained.

How much storage does a Bitcoin node need?

All blocks together are 776 GB, and the chain grew about 83 GB over the last year. Add the chainstate on top: the database of every unspent output, which your node reads for each transaction it checks.

Size of all Bitcoin blocks

776 GB

+83 GB in a year

650 GB725 GB800 GB
Oct 2025Oct 2026
Block headers and transactions only, no database indexes. Live from blockchain.com, as of 2026-10-14, refreshed every few hours.

Pick a node type and a drive to see how long it lasts, and how long the first download takes on your connection:

Storage calculator

Your drive

Block data today

776 GB

Fits, 78% full. At last year’s pace a 1 TB drive is full of block data around 2029.

First sync, download alone

≈ 17 hours

776 GB at full speed. Checking the blocks usually takes longer.

Block data from blockchain.com, 2026-10-14, growing about 83 GB a year over the last year. Future sizes carry that pace forward in a straight line, a rough guide only. Both node types also keep the chainstate (the UTXO set, several GB) on top. A pruned node still downloads every block once.

Use an SSD. A node constantly reads and writes the chainstate, and on a spinning disk the first sync can take many times longer. bitcoin.org asks for at least 100 MB/s.

How do you run a Bitcoin node?

Install Bitcoin Core, let it sync, leave it running. The hardware bar is low. These are bitcoin.org’s published requirements:

Pruned minimumRecommended
Disk7 GB750 GB
Memory256 MB2 GB
Download150 MB a day500 MB a day
Upload10 MB a day5 GB a day
SystemWindows 10+, macOS 14+, Linux, some ARM boardsThe same
  1. 1

    Get Bitcoin Core

    Download it from bitcoincore.org and check the signature before you install.

  2. 2

    Choose full or pruned

    Enough disk? Keep everything. Tight on space? Set a prune target in the settings; 550 MiB is the minimum.

  3. 3

    Let it sync

    The initial block download fetches and checks every block since 2009. Your wallet won’t show new payments until it catches up.

  4. 4

    Leave it on

    Once synced it only needs about one block every ten minutes. Open port 8333 if you want to serve other nodes too.

  5. 5

    Point your wallet at it

    Many wallets can connect to your own node, so they stop asking a stranger’s server about your balance.

How much bandwidth does a node use?

Downloads are steady and small once you’re synced: a few hundred MB a day. Upload is the big one, because your node sends old blocks to new nodes catching up. bitcoin.org puts it at around 5 GB a day with default settings.

8 + 2

outbound peers

full-relay + block-relay-only

200

connections max

Bitcoin Core default

≈ 5 GB

upload a day

default settings, bitcoin.org

≈ 250 MB

download a day

after the first sync

On a capped plan, Bitcoin Core’s maxuploadtarget stops serving old blocks once you hit a daily limit, and blocksonly skips relaying loose transactions. Turning off listening cuts your peers to the outbound ones. Your node still checks everything either way.

Does running a Bitcoin node earn you bitcoin?

No. Nodes aren’t paid. The block reward goes to whoever mines the block, and mining takes hashrate, which a node doesn’t have. What a node gives you is certainty that the bitcoin you receive is real, and a small, real vote for the rules you run.

If you’re curious what mining itself is like without buying a machine, the CloudMineCrypto app lets you start free: claim the free plan, add more with ads, games, offers and the daily check-in, and withdraw to your own wallet, Lightning included. Rewards are estimates and aren’t guaranteed, and a plan isn’t a share in any real machine or pool. Terms apply.

Frequently asked questions

What is a Bitcoin node?

A computer running Bitcoin software that downloads blocks and transactions, checks every one against the rules, and passes the valid ones on to other nodes. A full node trusts nobody: it verifies everything itself.

Do you earn bitcoin by running a node?

No. Bitcoin pays miners for finding blocks, not nodes for checking them. People run nodes to verify their own payments, keep their privacy and help the network.

How much storage does a Bitcoin full node need?

A full archival node keeps every block, over 750 GB in 2026, growing by roughly 80 GB a year. A pruned node checks the same blocks but keeps only recent ones, and can run in about 7 GB.

What is the difference between a full node and a pruned node?

Both download and verify every block. A full node keeps them all and can serve old blocks to others. A pruned node deletes old blocks after checking them, so it needs far less disk but can’t help new nodes sync.

Do miners need to run a node?

Someone in the chain does. Under Stratum V1 the pool runs the node and builds the block template. With Stratum V2 job declaration, a miner can use its own node to choose the transactions.

How long does it take to sync a Bitcoin node?

The first sync downloads and checks the whole chain, so it can take hours on a fast computer and days on a small one. After that a node only has to keep up with about one block every ten minutes.

Can I run a Bitcoin node on a Raspberry Pi?

Yes. bitcoin.org lists some ARM chipsets as supported. A fast SSD matters more than the CPU, and the first sync will be slow.

Sources and further reading

  1. Running a full node ¡ bitcoin.org
  2. Bitcoin Core system requirements ¡ bitcoin.org
  3. Operating modes: full nodes and SPV clients ¡ Bitcoin developer documentation
  4. getblocktemplate RPC reference ¡ Bitcoin developer documentation
  5. Reduce traffic: connections, upload target and blocks-only mode ¡ Bitcoin Core
  6. Stratum V2 Job Declaration Protocol ¡ Stratum V2 working group
  7. Blockchain size chart ¡ blockchain.com
  8. Bitcoin: A Peer-to-Peer Electronic Cash System (section 8, simplified payment verification) ¡ Satoshi Nakamoto, 2008

Live figures on this page come from the CloudMineCrypto API or from the public blockchain data services named next to them, refresh on a schedule, and are labelled where they appear. This guide is educational and not financial advice. CloudMineCrypto is not an investment product; rewards in the app are estimates and aren’t guaranteed.

You’ve read how it works. Now watch it happen.

Claim a free 8-hour mining plan in the CloudMineCrypto app and see your estimated BTC tick up from live network data. No hardware, no card.