When a transaction is broadcast, it reaches a node, which checks it against the rules before passing it on. Is the signature valid? Does the sender actually hold the funds? Has this been spent already? Anything failing those checks is dropped rather than forwarded. Valid transactions wait in the node's <a href="/glossary/mempool/">mempool</a> until a block producer picks them up. Every node repeats the same verification independently, which is why a bad transaction cannot simply be smuggled in from one corner of the network.
Not all nodes are alike. A full node holds the entire chain and verifies everything from the first block onwards. An archive node keeps every historical state as well, which is what block explorers and analytics tools need. A light client stores only block headers and asks others for the rest, trading some independence for the ability to run on a phone. Running your own full node is the difference between checking the rules yourself and taking somebody else's word for them.
A common muddle is treating node and <a href="/glossary/validator/">validator</a> as synonyms. Every validator or miner runs a node, but the vast majority of nodes never produce a block. They verify, store and relay, and that is exactly their power: block producers can only propose, while ordinary nodes decide what counts as valid. If producers pushed out blocks breaking the rules, honest nodes would reject them and the offending blocks would go nowhere.
This is what <a href="/glossary/decentralization/">decentralisation</a> actually looks like in practice. A network with many independently operated nodes, spread across jurisdictions and hosting providers, is harder to censor, coerce or quietly rewrite. A network whose nodes cluster with one cloud provider or one operator is far more fragile than its marketing usually admits.
Key takeaways
- Nodes enforce the rules; block producers only propose blocks, and invalid ones get rejected.
- A full node lets you verify balances and history yourself instead of trusting a third party's answer.
- The number of nodes matters less than how independently they are run and where they are hosted.
Node — frequently asked questions
Do I need to run a node to use crypto?
No. Wallets and exchanges query other people's nodes on your behalf, which is perfectly workable. Running your own removes that dependency: you verify your own balances, you cannot be fed a filtered view of the chain, and you leak less information about which addresses are yours. It is optional, but it is the most direct way to stop trusting intermediaries.
Does running a node earn money?
Generally not. A plain full node receives no reward; it costs you bandwidth, storage and electricity. Earnings come from producing blocks, which means mining or staking as a validator, and those roles carry their own hardware, capital and penalty considerations. People run ordinary nodes for privacy, self-verification and to strengthen the network, not for income.
New to crypto, or filling in the gaps? Work through the essentials in Learn, browse every term A–Z, or see live prices for the coins these concepts power.