What Is the Difference Between a Full Node and a Light Node?
Every crypto wallet or app has to get its information about the blockchain from somewhere, and the way it does that falls into one of two broad categories, each with a very different tradeoff between independence and convenience.
The short answer
A full node downloads and independently verifies the entire history of a blockchain, checking every transaction against the network’s rules itself. A light node, sometimes called a lightweight or SPV client, downloads only a small portion of that data and relies on full nodes elsewhere on the network to supply information it trusts rather than independently verifies in full.
What a full node actually does
Running a full node means storing a complete copy of the blockchain’s transaction history going back to its very first block, sometimes called the genesis block, and independently checking every new transaction and block against the network’s consensus rules before accepting it. This requires meaningful storage space, ongoing bandwidth, and a computer that stays connected and synced with the network, and it’s part of why full nodes matter for why transaction ordering matters so much across a blockchain: a node that verifies everything itself can confirm ordering and validity without taking anyone else’s word for it. In exchange, a full node operator doesn’t have to trust anyone else’s word about the state of the blockchain — they can verify it themselves, directly from the source data.
What a light node trades away
A light node skips almost all of that. Instead of storing and checking the full history, it downloads just enough data — typically block headers — to confirm that a transaction is included in the chain, and it relies on full nodes to supply the surrounding context. This is why light nodes power most mobile and browser-based wallets: they can run on a phone with limited storage and still function, whereas a full node’s storage and bandwidth requirements make it impractical for most everyday devices.
The tradeoffs, side by side
- Verification. Full nodes independently verify everything; light nodes trust data supplied by other nodes on the network.
- Resource use. Full nodes require substantial and growing storage and bandwidth; light nodes need only a small fraction of that.
- Setup effort. Full nodes typically take significant time to initially sync with the network; light nodes connect almost immediately.
- Practical use case. Full nodes suit dedicated infrastructure and enthusiasts who want independent verification; light nodes suit everyday wallets and apps prioritizing convenience.
Why this distinction matters beyond technical trivia
The number and distribution of full nodes across a network is part of what keeps a blockchain decentralized, since each independent verifier reduces reliance on any single party’s honesty. This connects to broader questions about how a network stays trustworthy without a central authority, similar to how decentralized oracles differ from centralized ones in spreading out where trust has to be placed. A network with very few full nodes concentrates verification power in fewer hands, even if millions of light-node wallets are actively using it day to day. This is also part of why a layer 2 network built to reduce transaction costs still depends on the underlying base layer’s full nodes for final security, even as everyday activity happens somewhere lighter-weight.
The bottom line
A full node trades convenience for independent verification, storing and checking the entire blockchain itself, while a light node trades that independence for something that fits on a phone, leaning on other nodes to supply trusted data. Neither approach is wrong for its purpose — they simply serve different needs, from someone running dedicated infrastructure to someone just checking a wallet balance between errands.