Miner vs node: who actually enforces the rules
A miner builds blocks; a node validates them. Pools do the mining on Bitcoin today — your 'miner' is a hashing appliance pointed at a pool, while your node (if you run one) is your own rulebook and verifier.
2026-10-19·updated 2026-10-19·3 min·pow.family research#bitcoin#mechanics#network
01
Two different jobs
| Mining (block production) | Full node (validation) | |
|---|---|---|
| Does what | Grinds nonces on candidates | Checks every block and transaction against consensus rules |
| Run by | Pools / large farms (solo ASICs are lottery tickets) | Anyone — a laptop or small VPS qualifies |
| Earns | Block rewards + fees | Nothing — it is your sovereignty and verification |
| Decides | Which candidate chain to extend | Which blocks your wallet and view of the chain accept |
The split matters for small miners: when you point an ASIC at a pool, the pool is the Bitcoin miner — it assembles block templates and broadcasts winners. Your machine rents guessing power to it. The rules are enforced by the thousands of nodes that would reject an invalid block even if every pool signed it.
02
Why a miner might still run a node
- Verify your own payouts instead of trusting an explorer (the Operations track's reconciliation habit).
- Escape pool-template censorship: some setups (especially Stratum V2) let miners build their own block templates.
- Watch the chain directly — mempool fees, retarget timing, fork chatter — with no third-party filter.
03
See it live on pow.family
Small PoW chains keep the distinction visible: on solo-mineable coins like MDS you ARE the miner, and every project page links the explorers and node tooling that play the validator role.