Glossary · Nodes and clients
Published 22 May 2025 · Updated 2 Nov 2026 · 14 min read
A light client is software that follows a blockchain without downloading and executing every block. It accepts headers through Bitcoin proof of work or Ethereum sync committee signatures. It checks requested data with Merkle proofs against those headers, while trusting the network's majority for transaction validity.
A light client keeps small block summaries, requests data with proofs from a full node, then checks those proofs against the summaries. Different chains deliver summaries differently. The technical terms are block header, Merkle root and Merkle branch. A light node runs this blockchain client software. Bitcoin calls the approach Simplified Payment Verification, or SPV.
| Full node | Light client | Wallet that trusts an RPC endpoint | |
|---|---|---|---|
| Downloads | Full nodeBlocks and state needed for independent validation | Light clientHeaders or committee updates, plus requested data | Wallet that trusts an RPC endpointResponses supplied by its endpoint |
| Checks consensus rules | Full nodeEnforces consensus rules and validates transactions | Light clientChecks consensus evidence, without executing transactions | Wallet that trusts an RPC endpointDoes not independently check consensus rules |
| Checks that data is in the chain | Full nodeChecks transactions within downloaded blocks | Light clientChecks Merkle branches against accepted roots | Wallet that trusts an RPC endpointAccepts the endpoint's claims without verification |
| Trusts | Full nodeIts rules and possibly a starting checkpoint | Light clientConsensus majority and any required starting checkpoint | Wallet that trusts an RPC endpointThe RPC provider for every chain claim |
| Privacy | Full nodeCan read locally rather than querying a server | Light clientDepends on filters, peers and requested data | Wallet that trusts an RPC endpointExposes requests and network activity to its provider |
The anchor depends on the chain. Bitcoin checks proof of work and follows the most-work chain. Ethereum requires BLS signatures from 342 of 512 sync committee seats to advance finalized headers. CometBFT checks signatures representing more than 2/3 of voting power. Mina and ZK light clients use succinct cryptographic proofs, or SNARKs. A Merkle branch links data to an already accepted header.
These checks do not validate the transactions themselves. An RPC-only wallet performs none of these checks. A server can omit activity, and Electrum trusts its server about unconfirmed transactions. A full node instead enforces the rules governing blocks and their contents. The ethereum.org nodes page says light nodes have the same security guarantees as a full node. On 2 November 2026, its dedicated guidance describes equivalence as a future goal, not a present guarantee.
Section 8 of the October 2008 white paper describes SPV for the Bitcoin network, without running a full node. Each block header occupies 80 bytes, including a 32-byte Merkle root. The paper estimates 4.2 MB of headers per year. On 2 November 2026, the complete header chain at height 974,285 occupies 77.94 MB.
The 12 sibling hashes total 384 bytes and link this transaction to its block, showing sides and parent hashes.
The header and proof together occupy 464 bytes, compared with 1.68 MB for the entire block.
The proof establishes inclusion only. It cannot establish transaction validity or reveal other transactions a server omitted.
After 12 double SHA-256 steps, the computed root matches the Merkle root stored in the header.
Changing one transaction ID byte changes every hash above it, so the computed root no longer matches.
Block, transaction and branch data come from mempool.space, 2 November 2026, checked by the page team through hashing.
BIP 37 introduced the Bloom filter approach in October 2012, letting wallets request matching transactions. A September 2014 study found that clients risked exposing almost all their addresses. BIP 157 later described most implementations as offering virtually zero privacy. Bitcoin Core 0.19.0.1 disabled serving Bloom filters by default in November 2019 to remove known denial-of-service vectors.
BIP 157 and BIP 158 define one compact block filter per block, checked locally. One honest peer lets clients identify correct filters, then fetch matching blocks from any peer. Filters are not committed in blocks. The Lightning node LND can use the Neutrino light client as its back end. Wasabi Wallet 2.8.0 obtains filters over P2P in June 2026. Electrum instead maintains about 10 server connections for headers. One main server sees wallet addresses and can lie by omission.
LES stopped working after the Merge upgrade, and Geth removed it in November 2023. Ethereum's Beacon Chain instead supports the sync committee introduced with Altair on 27 October 2021. Each period assigns 512 seats for 8,192 slots, about 27.3 hours. Advancing a finalized header normally requires at least 342 signatures. A light client can follow period updates rather than downloading every block summary.
The sampled finality update has 510 of 512 signatures for the attested header at slot 15,568,436.
With at least 342 valid signatures, the finalized header may advance when the other update checks pass.
With 256 to 341 signatures, participation exceeds half the recent best of 510, so only the optimistic header may advance.
At 255 signatures or fewer, neither view advances. The client waits for sufficient participation.
Signature bits come from public beacon API nodes, 2 November 2026. Thresholds follow the Altair light client specification.
Starting from a trusted root, the client verifies a BLS aggregate signature over the attested header. Merkle branches connect it to finality, the next committee and the execution payload header. Its state root anchors blockchain state, with eth_getProof returning Merkle Patricia Trie account and storage proofs. EIP-6800 estimated in March 2023 that account proofs average close to 3 kB. A finality update is about 2.1 kB. A full update each period is about 26.9 kB, roughly 8.6 MB yearly. The light client checks these connections without executing transactions.
Ethereum clients on 2 November 2026 include Helios 0.12.0, Nimbus's BETA light client, Lodestar 1.43.0, Geth blsync and Colibri 3.0.3. Lodestar's light client moved to its own repository in May 2026. ethereum.org lists all but Colibri and calls none production-ready. Portal Network remains unfinished. Weak statelessness remains research work. Most Verkle EIPs are Stagnant, with no stateless client EIP scheduled for a fork. Glamsterdam replaces the execution payload header with its block hash on Sepolia and Hoodi, requiring a separate execution header fetch. No mainnet date is set.
Storage volume does not identify what a program validates. This comparison separates downloaded material, local checks and outside assumptions. A pruned full node still validates blocks, while a light client follows selected consensus evidence. Requirements and implementation details below reflect 2 November 2026.
| Client | Downloads or stores | Checks itself | Trusts |
|---|---|---|---|
| Bitcoin full node | Downloads or storesFull blocks, with at least 550 MiB retained when pruned | Checks itselfValidates blocks and transactions under Bitcoin consensus rules | TrustsIts validation rules, not a server's transaction claims |
| Bitcoin SPV client | Downloads or storesEvery 80-byte header plus requested transactions and Merkle branches | Checks itselfValidates chain work and transaction inclusion against accepted roots | TrustsHonest hash power and servers for omitted activity |
| Neutrino client | Downloads or storesHeaders, compact filters and blocks matching wallet activity | Checks itselfChecks filter consistency across peers and matching block data | TrustsHonest hash power and at least one honest filter peer |
| Ethereum full node | Downloads or storesBlocks and state, potentially retaining only 128 recent state versions | Checks itselfExecutes transactions and enforces Ethereum consensus rules independently | TrustsIts validation rules and any trusted recent starting block |
| Ethereum light client | Downloads or storesCommittee updates, requested account data and authentication branches | Checks itselfVerifies committee signatures, finality and requested values against roots | TrustsA recent checkpoint and an honest sync committee supermajority |
| Celestia light node | Downloads or storesBlock summaries and 16 random samples per block | Checks itselfChecks data availability sampling results within a seven-day window | TrustsConsensus and sampling assumptions, without executing every transaction |
| ZK light client | Downloads or storesSuccinct consensus proofs for verification on a destination chain | Checks itselfVerifies source consensus through a cryptographic verifier contract | TrustsSource consensus majority, verifier correctness and, for SP1 Helios, a guardian |
A valid light client response does not establish that a server supplied everything. Compare four readers here, from a single-server Bitcoin wallet to Ethereum committee verification. The results distinguish false data, missing data and delayed data, rather than treating every server lie alike.
A fabricated transaction fails the Merkle proof for verifying clients. An RPC-only wallet accepts the server's claim.
One server can hide a transaction. BIP 157 exposes omissions with one honest peer, while Ethereum log queries lack efficient completeness proofs.
An incorrect Ethereum balance fails the account proof against the accepted state root. Bitcoin wallets instead track their outputs.
Fake headers fail proof of work or committee checks. A one-server SPV wallet cannot see a heavier chain, and an RPC-only wallet checks nothing.
Clocks only partly expose an old head. Additional peers can reveal fresher data that a single server withholds.
No light client here catches an invalid block accepted by a dishonest consensus majority, because none executes its transactions.
Outcomes follow the Bitcoin white paper and developer guide, BIP 157, Ethereum light client specifications, EIP-1186 and EIP-7745.
Weak subjectivity means a proof-of-stake client needs a recent trusted checkpoint to resist a long-range attack. Electra's window is about 15.7 days, while Gloas rules shorten it to about seven days. Helios warns after two weeks, and Nimbus requests a root about one to two weeks old. CometBFT explains the danger: old, unbonded voting keys can be bought to fabricate historical forks without current bonding costs.
Not every light client follows each intervening block. Some verify changing validator sets, some sample whether data is available, and others verify compressed computations. These differences matter when another blockchain, rather than a wallet, performs the checks.
CometBFT checks signatures exceeding 2/3 of the new set's voting power. Bisection skips intermediate headers but requires older-set support, defaulting to 1/3 in CometBFT and 2/3 in Hermes. The trusting period must also remain shorter than the unbonding period. In IBC, proven misbehavior freezes the client. Elsewhere, Celestia checks availability with 16 random samples per block within seven days. NEAR follows epoch block producers with approval above 2/3 of stake. Mina instead uses recursive proofs, with about 22 KB for non-consensus nodes.
A cross-chain bridge can verify source consensus rather than accept an oracle's claim. SP1 Helios is a ZK light client that checks source consensus inside the destination chain. Its Groth16 proofs are about 260 bytes, costing roughly 270,000 gas to verify. PLONK uses about 868 bytes and 300,000 gas. A guardian can change its verification key unless that role is relinquished. For blockchain rollups, ethereum.org describes checking deposit evidence before releasing tokens.
Small downloads do not remove dependencies on peers, signers or verification code. These six failure modes affect different layers of a design. Separating them helps teams distinguish an unavailable answer from an answer that should never be accepted.
A server can hide activity without fabricating anything. Ethereum has no efficient log index in November 2026, so proving that a log query is complete remains expensive.
An eclipse attack isolates a reader. Multiple peer-to-peer connections help, but partitioning or Sybil identities can defeat them, leaving valid yet outdated responses.
A stale checkpoint can anchor a convincing historical fork. Proof-of-stake readers need a recent trusted starting point, not merely internally consistent signatures.
Sync committee members cannot be slashed for signing a wrong root. EIP-7657 warns that a dishonest supermajority can present non-canonical finality.
Electrum servers learn script hashes and IP addresses. BIP 157 sends no wallet data, but Ethereum RPC providers still receive every query.
Wormhole in February 2022, Nomad in August 2022 and BNB Bridge in October 2022 lost funds through broken verification. Their consensus mechanisms did not fail.
The design began with payment inclusion, then expanded to address privacy and different consensus systems. This timeline follows eight protocol and implementation changes. It separates proposed ways to obtain data from the software releases that made them available.
The Bitcoin white paper introduces Simplified Payment Verification in section 8. Readers can connect payments to the chain without executing transactions.
BIP 37 lets peers select transactions matching a client's Bloom filter. The client no longer needs every transaction to find possible matches.
BIP 157 and BIP 158 define filters that clients download and match locally, rather than sending wallet-specific filters to peers.
Bitcoin Core 0.19.0.1 stops serving Bloom filters by default. The change removes well-known denial-of-service vectors from the default configuration.
Ethereum adds sync committees on 27 October 2021. Their signatures let constrained readers follow consensus without processing every transaction themselves.
Geth removes its LES code on 23 November 2023 after it stops working following the Merge. Version 1.13.6 follows in December 2023.
Wasabi Wallet 2.8.0 obtains compact filters from the Bitcoin P2P network. This replaces its centralized server for that data.
Helios 0.12.0 is released. Glamsterdam changes light client headers on Sepolia on 6 October 2026 and Hoodi on 26 October 2026.
Adding verification to a wallet, app or bridge starts with boundaries, not a client name. We separate what the application can verify from what it still assumes. In crypto wallet development, that means deciding how data reaches the user, how it is authenticated and what happens when verification cannot finish.
PixelPlex was founded in 2007 and began blockchain work in 2013. Our Qtum Wallet case study covers Android and iOS, Qtum API integration, on-device encoding of private keys and all transaction data, and a 12-word seed phrase backup. This demonstrates wallet integration experience, not a light client implementation.
Discuss verification boundaries for your next application
We can discuss your data sources, verification requirements and remaining assumptions before you choose an implementation approach.
Discuss your projectGet updates about blockchain, technologies and our company
We will process the personal data you provide in accordance with our Privacy policy. You can unsubscribe or change your preferences at any time by clicking the link in any email.Services
Blockchain
Blockchain consultingStrategy, architecture, feasibility
Crypto wallet developmentSelf-custody, MPC, cards on top
Cryptocurrency exchange developmentTrading venues, liquidity and protocols
Tokenization servicesRWA, funds, collateral
Crypto payments developmentAccept, settle and pay out in crypto
Smart contracts developmentDesign, build, audit
Blockchain integration dApp development DeFi development NFTs Tokens Web3 development All blockchain services All servicesNetworks
Canton developmentDaml apps, wallets, settlement, validators
Official Partner
Ethereum developmentSmart contracts, L2s and dApps
Solana developmentHigh-throughput programs and dApps
TON developmentMini apps, wallets, Telegram ecosystem
Official Partner
Hedera developmentHashgraph apps and token services
Exclusive Partner
Hyperledger developmentPermissioned networks for enterprises
Certified Partner
Cardano Algorand Stellar Avalanche Bitcoin Polygon All networks All servicesAI & ML
AI agents developmentConnect tools and automate multi-step workflows
RAG developmentFind answers across your company’s documents and systems
AI copilot developmentAdd useful assistance to your product or internal tools
LLM developmentCustom and fine-tuned models for your domain
Private AI deploymentRun models in your own environment
AI consultingUse cases, feasibility and a roadmap
Generative AI development Machine learning development Computer vision Chatbot development ChatGPT integration Deep learning development All AI services All servicesData & analytics
Data engineeringPipelines that keep your data reliable
Data platform developmentOne source of truth for analytics
Analytics & dashboards developmentBI your teams actually use
Predictive analyticsForecasts built on your own history
Data strategyWhere data can pay off first
Data visualizationDashboards and visual stories from your data
Data science development Development of data marts All data services All servicesSoftware
Product discoveryValidate scope and cost before you build
MVP developmentA launch-ready first release
Web application developmentPlatforms, portals and internal tools
Mobile app developmentiOS, Android and cross-platform
SaaS developmentMulti-tenant products that scale
Software integrationConnect the systems you already run
Infrastructure & cloud cost UI/UX design IT consulting QA & software testing R&D Serverless development All software services All servicesSecurity & compliance
Smart contract auditsFind vulnerabilities before launch
Transaction monitoring developmentIntercepta inside your systems and processes
Security assessmentsTest apps, infrastructure and processes
Data security servicesProtect sensitive data across its lifecycle
Cloud security servicesSecure cloud workloads and configurations
DAML smart contract auditReview DAML contracts before they go live
All security services All servicesSolutions
Products, APIs and platforms
New
Products and engineering to build and operate on Canton.
In production 55M API requests served in 8 months
Crypto APIBlockchain data for your applications.
Power in numbers 6 TB Data storage. 500K Tokens indexed
RWA platformA foundation for your asset tokenization platform.
Time to launch 2–4 weeks Branding & setup. 90% more cost-efficient
DocFlowBlockchain-based document management.
Use case & value 100% Secure workflows. Zero third-party risks.
OTC Hawk Arbitrage Bot Book a solution consultWork
450+ projects. 250+ clients. 3 unicorns in portfolio
The first non-custodial wallet built natively for Canton
TON ecosystemA series of improvements for The Open Network
Mining platformEnvironmentally friendly web platform for Bitcoin pool mining
Mantra DAOCommunity-governed DeFi: 60+ staking pools, $23M TVL
Canton TON Web3 & DeFi Digital Assets & Tokenization AI & Data Intelligence IoT & Edge Computing Consulting See all projectsIndustries
Trusted by startups, small businesses, and enterprises
Banking, payments, lending, insurance, capital markets
Real estate software developmentInvestment, property operations, tokenization
Retail & commerce software developmentCommerce, loyalty and fulfillment
Supply chain software developmentTraceability and connected operations
Healthcare software developmentPatient services, data and connected systems
Banking software developmentCore banking, digital channels, payments
Fitness Education Oil & Gas Insurance Construction TravelCompany
From R&D to launch, we bring any of your ideas to life
Engineering partner. Product builder. Since 2007.
Technical experience 19+ years All competencies on board. Scalable team.
AchievementsIndustry recognition & awards.
Delivering real value 4.9 Clutch ratings. 150+ awards
Contact usDiscuss your project.
Quick response 30 min Average reply time. Offices in 6 countries
BlogDive into the latest software trends.
Fresh insights 500+ Articles in blockchain, AI, big data, AR/VR
Team Careers Social responsibility Glossary