A full node independently checks blocks and transactions against Bitcoin’s consensus rules. It does not accept a block as valid simply because a miner or another peer says so. Bitcoin.org’s node guide.
Validation and storage are different
An archival node retains historical block data. A pruned full node can validate the history and then discard older block files to reduce disk use. Pruning changes what it can serve or rescan locally, not whether it checks consensus rules. Pruning and node operation.
This is why “a full node stores the entire blockchain” is an incomplete definition.
Nodes and miners
Mining proposes a new block. Validation decides whether a received block follows the rules that a node’s operator has chosen to enforce. A user can run a validating node without mining. These roles often interact, but they should not be treated as synonyms. Full-node functions.
Peers, not a central server
Nodes exchange information with peers. Network messages help them discover other nodes, synchronize block data, and relay transactions. An individual node’s view is built from received data and its own validation. Peer-to-peer documentation.
Operating a node does not make its owner a one-person rulemaker, and node counts are not a simple ballot deciding consensus.
Why connect a wallet to your own node?
A wallet that uses your node can rely on your validation rather than a third party’s report about the chain. That does not replace wallet backups, guarantee anonymity, or protect an insecure signing device.
For practical setup, use the node guide and check its current requirements. Disk, bandwidth, and synchronization needs change as the chain grows.