Node Types

Bitcoin nodes come in different types, each with different capabilities, resource requirements, and trust models. Understanding node types helps you choose the right setup for your needs.

Full nodes download and validate the entire blockchain:

• Downloads ~600GB+ blockchain data
• Validates all transactions and blocks
• Maintains complete UTXO set
• Maximum security and privacy; requires significant resources
• Best for: security-critical and privacy-sensitive applications, contributing to the network, development and testing

Pruned nodes validate everything but don't store full history:

• Validates all blocks
• Stores only recent blocks (~2GB)
• Maintains UTXO set
• Good security, lower storage; can't serve historical data
• Best for: limited storage, full validation without needing historical data

Archival nodes store complete blockchain history:

• Full blockchain storage
• Can serve historical data
• Maximum storage requirements
• Best for: blockchain analysis, historical data access, research, public services

SPV nodes download only block headers:

• Downloads ~80 bytes per block
• Minimal storage (~50MB)
• Relies on full nodes; less privacy; faster sync
• Best for: mobile wallets, lightweight clients, limited resources, quick setup

Full and pruned nodes can be run over Tor for IP privacy and eclipse mitigation.

AssumeUTXO (in Bitcoin Core 26+) allows a new node to start from a snapshot of the UTXO set at a recent block height instead of verifying every block from the genesis. The node downloads a signed snapshot (from a built-in or external source), loads the UTXO set, and then syncs only the remaining blocks to the chain tip. This can reduce initial sync time from days to hours. The node still performs full consensus validation for all blocks it downloads; the trust is only that the snapshot is correct at that height, and the BIP process and built-in defaults are designed to minimize risk. Useful for pruned and full nodes that want to reach tip quickly, then optionally verify history in the background.

Block-relay-only is a connection mode where the node does not exchange transaction (inv, mempool) data with that peer, only blocks and compact blocks. This reduces privacy leakage (peers cannot directly tie your transactions to your IP) and bandwidth. Bitcoin Core uses some block-relay-only outbound connections by default.

Checking Node Type

• Bitcoin Core Internals - Node implementation
• P2P Network Protocol - Network communication
• Installing Bitcoin - Setup guide

• Bitcoin Core Documentation
• Running a Full Node