A light node is a stripped-down participant in a blockchain network that trades independence for speed and low resource use. Rather than storing every block and transaction like a full node, it downloads only block headers, compact summaries containing a timestamp, the previous block's hash, and a Merkle root, and leans on full nodes to supply whatever transaction data it needs.
The approach traces back to Simplified Payment Verification, described in the original Bitcoin whitepaper. A light node checks that a transaction belongs to a block by requesting a Merkle proof: a short chain of sibling hashes linking the transaction to the Merkle root already stored in the header it verified. If those hashes reconstruct the correct root, inclusion is confirmed, without the node ever downloading the block's full contents.
The payoff is practical. Fully syncing a Bitcoin or Ethereum node means processing hundreds of gigabytes of history; a light node needs only a small fraction of that data, so it can run on phones, browser extensions, and other storage-constrained hardware. Most mobile crypto wallets, including early tools like Electrum, are built on this model.
The trade-off is trust. Because light nodes depend on whichever full node or provider feeds them data, a dishonest peer could in theory withhold or misrepresent information. Newer designs try to close that gap: fraud proofs let full nodes flag invalid blocks to light clients, and emerging zero-knowledge light clients let a device verify a succinct cryptographic proof of chain validity instead of trusting a single source outright.