Skip to Content
DocsResearchLight Clients68. Light Clients Verification

Light Clients & Verification

The original can be found at Zenon Developer Commons .

Research into trustless verification models for resource-constrained environments.


Overview

Zenon’s dual-ledger architecture enables lightweight verification without global state. Light clients can verify chain progress and account-chain updates using only:

  • Momentum headers
  • Compact state proofs
  • Local account-chain data

This aligns naturally with SPV-style verification, making browser native and mobile clients viable as first class network participants.


Key Concepts

Header-Only Verification — Light nodes verify chain progress by validating Momentum headers (Pillar signatures, difficulty, weight) without downloading full blocks or global state.

State Proof Bundles — Compact verification primitives that prove account-chain transitions without Merkle proofs or global state access.

Browser as Peer — Modern browsers can perform cryptographic verification using WASM and P2P transports, enabling trustless participation without RPC gateways.


Documents in This Section

  • Momentum Header Verification — How light nodes verify chain progress: Pillar eligibility, chain continuity, and account-chain finality using only headers.

  • State Proof Bundles — Compact verification primitive for account-chain transitions. Explains why Merkle proofs aren’t needed in the dual-ledger model.

  • Browser Light Client Overview — Early notes on minimal browser client: header sync, local signing, micro PoW generation, and transaction relay.

  • Browser Light Client Architecture — Comprehensive research on browsers as verifiable peers. Covers verification responsibilities, networking, and state reconstruction.

Last updated on