Light Node

How light nodes work

A light node downloads only block headers — small data structures (~80 bytes for Bitcoin) containing block metadata. To verify specific transactions:

• The light node receives a transaction along with a Merkle proof showing the transaction is in a specific block.
• The light node verifies the Merkle proof against the block header.
• This proves the transaction was included without downloading the full block.

This is sometimes called Simplified Payment Verification (SPV) for Bitcoin specifically.

Why light nodes matter

The trade-off:

• Full nodes — verify everything, require significant disk space and bandwidth.
• Light nodes — verify a subset, can run on phones and embedded devices.

For most users, full nodes are impractical (Bitcoin requires ~600GB; Ethereum 1TB+). Light nodes enable mobile wallets, browser-based clients, and IoT integrations.

Trade-offs vs. full nodes

What light nodes give up:

• Full validation — they trust full nodes to enforce protocol rules correctly.
• State queries — most state queries require asking a full node, which can lie or be unavailable.
• Privacy — light nodes typically reveal what they're querying to whoever serves them.

What they gain:

• Resource efficiency — orders of magnitude less storage, bandwidth, CPU.
• Mobile/embedded compatibility — can run on devices that couldn't run full nodes.
• Faster startup — no multi-day initial sync.

Where light nodes are used

• Mobile wallets — most mobile crypto wallets are technically light nodes or query light-node infrastructure.
• Browser-based wallets — same.
• Light node implementations — Electrum (Bitcoin), Geth's light mode (Ethereum).
• Bridges and oracles — sometimes use light-node verification.

Light client improvements

Active research and development:

• Snap sync (Ethereum) — fast initial state download without verifying entire history.
• Stateless clients (Ethereum future) — light client that doesn't need to maintain state at all.
• Plumo, Mina — chains designed specifically for light-client efficiency, often using ZK proofs.
• Helios — Ethereum light client using sync committee from beacon chain consensus.

These efforts aim to reduce light-node trust assumptions while maintaining efficiency.

What individuals should know

For typical users:

• Most wallets are functionally light clients under the hood.
• Privacy implications — query patterns reveal information to whoever serves the data.
• For high-value or privacy-sensitive use — running a full node provides stronger guarantees, though with operational cost.
• Trust model — light clients trust the broader full-node network to be honest in aggregate.

For most use cases, light-client infrastructure works well enough. Full nodes matter most for users with specific security or privacy concerns.