A Full Node enforces Bitcoin consensus rules independently. It derives valid state from received data; peer count and device branding add no voting weight to its conclusions.
The node checks headers, Proof of Work, block links and UTXO transitions. Connecting a block requires existing unspent outputs, satisfied scripts and correct issuance limits. Greater work selects a different valid branch; it cannot override validity rules. [Bitcoin Core v29.0: validation]
Initial startup downloads and processes history. Under defined conditions, Bitcoin Core assumevalid may skip old script checks; assumevalid=0 disables this optimization. AssumeUTXO starts from a snapshot matching an approved hash and validates history in the background. An available current state is not necessarily completed historical validation. [Bitcoin Core v29.0: validation] [Bitcoin Core v29.0: AssumeUTXO]
After processing, a pruned node deletes old block files but keeps current UTXO state and validates new blocks. An archival node retains old blocks. This affects historical serving and rescanning; SPV, by contrast, does not validate every transaction and state in the same way. [Bitcoin.org: running a full node]
A running node does not protect payments if the wallet still checks them through another server. Check its actual data and broadcast paths. Nodes can operate without private keys; custody and signing are separate functions. Independent validation alone removes neither network metadata nor backup errors. [Bitcoin.org: running a full node] [Bitcoin Core v29.0: RPC security]
P2P connections carry blocks and transactions; RPC lets applications control the node and possibly a wallet. Opening an inbound P2P port is therefore different from publishing RPC. Bitcoin Core recommends keeping RPC off the public internet and uses an authentication cookie for local clients. [Bitcoin Core v29.0: RPC security]
Check network, blocks, headers and initialblockdownload in getblockchaininfo; getchainstates distinguishes snapshot state from background validation. A green icon or connection count alone proves no complete verification. Finally check that the wallet reads this node and that its block tip is not stale. [Bitcoin Core v29.0: AssumeUTXO] [Bitcoin Core v29.0: validation]
Trust, then verify — or verify directly
A wallet connected to someone else’s server asks that server about balances and transactions. A wallet connected to your own full node checks the same history against rules you selected and reduces what the server can learn about your addresses.
For the clearest picture, read this entry together with Bitcoin, Timechain, Transaction, UTXO, Proof of Work. The reverse links also lead from Bitcoin, Satoshi Nakamoto, Timechain, Proof of Work.
01Does a full node mine bitcoin?+
Not by itself. A full node validates blocks and transactions. Mining repeatedly hashes candidate block headers; the two roles can run together but are technically distinct.
02Do I need the entire blockchain forever?+
A pruned node validates the full chain during initial synchronization and then discards older block files while retaining the current UTXO set and enough recent data to operate.