network

light node

A light node, also called an SPV client, downloads only block headers instead of the full blockchain. It can verify that a transaction is included in a confirmed block without storing the entire transaction history, making it practical for mobile wallets and everyday use.

A light node, formally known as an SPV client after the simplified payment verification method described in the Bitcoin whitepaper, is a type of Bitcoin software that does not download or store the full blockchain. Instead of keeping every transaction ever recorded, a light node downloads only block headers, which are small summaries of each block containing the hash of the previous block, a timestamp, and a few other fields. This reduces the storage and bandwidth requirements dramatically compared to running a full node, which currently requires storing hundreds of gigabytes of data.

To verify a payment, a light node uses a cryptographic proof called a Merkle proof. When a full node tells the light node that a particular transaction is in a block, it provides a compact chain of hashes that the light node can check against the block header it already has. This allows the light node to confirm that the transaction is part of a block without downloading the full block itself. However, this method relies on being connected to at least one honest full node. A light node cannot independently verify that the block it is checking follows all the consensus rules, only that it exists in the chain with a certain amount of proof of work behind it.

The trade-off is one of convenience versus security. Full nodes are self-sovereign: they verify every rule themselves and do not trust anyone. Light nodes are convenient: they work on phones and low-storage devices, sync quickly, and are practical for everyday payments. Most mobile wallets, including many popular bitcoin apps, operate as light clients. Users who want to transact without trusting a third party while accepting slightly reduced privacy and security can run a light node. Those who want complete trustlessness and to contribute to network resilience should run a full node.

Frequently asked questions

What is the difference between a light node and a full node?

A full node downloads and validates the entire blockchain from the genesis block to the present. It independently checks every transaction and every block against all of Bitcoin's consensus rules, trusting no one. A light node downloads only block headers and relies on full nodes to provide transaction data when needed. This makes it far less resource-intensive, but it means the light node cannot verify consensus rules on its own. For most users who want to receive and send payments, the trade-off is acceptable. For those who want to contribute to Bitcoin's security or run a business that depends on trustless verification, a full node is the appropriate choice.

Is using a light node less private than a full node?

Yes, to some extent. A full node downloads all transactions broadcast to the network, so no external party can tell which transactions the node owner is interested in. A light node, by contrast, must ask a server for information about specific addresses or transactions. This request reveals to the server which addresses the user is monitoring. Various techniques such as client-side block filtering are designed to reduce this privacy leakage, and some modern light wallets implement them. Still, for users with strong privacy requirements, running a full node or using a privacy-focused tool on top of a full node provides significantly better protection.

Do mobile bitcoin wallets use light nodes?

Most mobile bitcoin wallets operate as light clients in some form. Storing and validating the entire blockchain on a smartphone is impractical due to storage constraints and the processing power required. Some wallets connect to a trusted server run by the wallet provider and request transaction information on behalf of the user. Others implement SPV or client-side filtering to reduce trust requirements. A small number of mobile solutions are designed to connect to the user's own full node, combining the convenience of mobile access with the trustlessness of running your own node.