Bitcoin is often described as a network run by computers around the world, which can make a "node" sound like a mysterious machine hidden somewhere in the cloud. It is nothing of the sort. A node is simply a computer running Bitcoin software and talking to other nodes — often something as modest as a small single-board computer tucked behind a home router. What makes it matter is not the hardware but the job it does.
That job is verification. When a node receives a new block or transaction, it checks for itself that the rules of Bitcoin were followed: that the block's proof of work is valid for the required difficulty, that signatures are correct, that the coins being spent actually exist and were not already spent, and that the miner did not award itself more than the allowed block subsidy plus fees. This is not a figure of speech. If a single consensus rule is broken, the node rejects the block outright — no appeal, no discussion. For that node, the block simply is not Bitcoin.
It is worth separating two words that get used interchangeably. The client is the software, the thing that holds the rules; Bitcoin Core is by far the most widely run, though other implementations exist, such as Bitcoin Knots. The node is that software running on a machine and applying the rules on its operator's behalf. The client carries the rulebook; the node enforces it for you.
Here is the part that surprises people: the protocol pays node operators nothing. No newly issued bitcoin, no yield, no block reward. The subsidy and transaction fees go to the miner who finds the block, not to the thousands of nodes that check it. Running a node costs you storage, electricity, bandwidth and a little time, and returns no money at all. So why do it? Because a node serves you first. Without your own, receiving a payment means trusting a third party's word that the transaction is real, confirmed and rule-abiding. With your own, you verify directly that the coins are valid, that no extra units were conjured into existence, and that the transaction sits in the chain you recognise as Bitcoin. The elegant twist is that game theory quietly replaces morality: nobody has to run a node out of altruism to "protect the network." Each operator verifies out of self-interest, and the sum of those independent checks is what enforces the rules across the whole system. For anyone curious enough to try, a node is also surprisingly approachable to set up — a few hundred euros of dedicated hardware, or far less on a machine you already own.
This is also what people mean when they say nodes "decide." A miner produces blocks; a company or exchange can fund developers, run marketing or supply liquidity. None of them can install software on your machine. If a block breaks your node's rules, your node rejects it — and if enough users and economic actors do the same, the miner will have spent real energy producing a reward that this part of the economy refuses to recognise as bitcoin. To change Bitcoin without causing a lasting split, then, you have to convince enough operators to run the new rules. That is not impossible; it is exactly how Bitcoin evolves. Developers propose, the ecosystem debates, software is published, and each node operator decides whether to adopt it. SegWit in 2017 and Taproot in November 2021 both activated that way, after winning broad enough support. What does not exist is a lever to force everyone to follow.
The asymmetry is sharpest for a hard fork — a change that would make blocks the current rules reject suddenly valid. To have new rules accepted as still Bitcoin, you need very broad agreement; to refuse them, an operator does nothing at all, keeping the software they already run, which will reject the incompatible blocks on its own. A soft fork works differently, because it only tightens the rules: blocks valid under the new, stricter rules are still valid under the old ones, so older nodes keep accepting them even without checking the new restrictions. But a soft fork can never make valid something the current rules already forbid — you cannot use it to lift the 21-million supply cap to 23 million, or to raise the block-size limit directly. Those would require the kind of broad, voluntary adoption that no single actor can manufacture.
None of this is the whole picture — full nodes are one type among several, and other blockchains apply similar logic in their own ways. But the core idea carries most of the weight: Bitcoin's rules are not enforced by an authority at the top. They are enforced at the edges, by whoever chooses to verify them, one independent machine at a time. This is general market and technology commentary, not investment advice or a recommendation to buy or sell any asset.