Light Node
Pronunciation: LYTE NOHD
Definition
A light node participates in a blockchain network with reduced storage or computation, relying on compact proofs or fuller peers for selected data. It may store headers, request account or transaction proofs, relay limited messages, and maintain wallet-relevant state without retaining or executing the entire blockchain. A light node or client verifies reduced evidence rather than downloading and checking all chain data.
Overview
Meaning and scope
A light node runs software that performs fewer duties than a full validating node . It may store headers, request account or transaction proofs, relay limited messages, and maintain wallet-relevant state without retaining or executing the entire blockchain.
How it works
Some light nodes independently verify consensus and inclusion, while others trust remote RPC servers for balances and history. Reduced resources can improve accessibility but may weaken privacy, availability, and protection against dishonest peers. Operators should document which checks are local, diversify data providers, authenticate peers, and detect stale chain views. A light node should not advertise full validation if it cannot enforce all rules. Payment processors handling significant value generally need full-node or strongly verified light-client confirmation rather than one server response.
Operational checks and limits
Implementation note: Light nodes save resources, but security depends on which consensus and state claims they verify independently versus obtain from peers. A light node participates in a blockchain network with reduced storage or computation, relying on compact proofs or fuller peers for selected data. A light node or client verifies reduced evidence rather than downloading and checking all chain data. Its actual security depends on the protocol’s proofs and trusted or peer-supplied information.
Practical example
A mobile wallet uses authenticated block information to display a receipt while a merchant backend conducts its own acceptance checks.
Distinctions
A light client trades verification scope and resource use against a full node; it is not simply a full node with old blocks deleted.
How to evaluate it
Node roles differ in the information they retain and the checks they perform; an application relying on Light Node should know whether its provider verifies chain rules independently, supplies historical data, or merely forwards another system’s response. When evaluating Light Node, to troubleshoot a missing deposit, compare chain inclusion, indexing progress, and application notification separately; a delayed balance display does not always mean an absent transaction. Related concepts: node; node.
Example
A mobile wallet uses authenticated block information to display a receipt while a merchant backend conducts its own acceptance checks.
Comparison
A light client trades verification scope and resource use against a full node; it is not simply a full node with old blocks deleted.
Key Takeaway
Know the proof and trust assumptions of light verification.
Sources
- Ethereum Documentation: Networking Layer — Ethereum Foundation (2026-07-30)
- Bitcoin Developer Guide: P2P Network — Bitcoin.org (2026-07-30)