← Back to news

LayerZero’s Zero: Decoupling Execution From Settlement

2026-02-17
Zero is Live

Last week LayerZero announced Zero, a Layer-1 that separates execution from settlement and shifts validation away from full state re-execution. The backing includes Citadel, ARK, DTCC, ICE, and Google Cloud. Institutional participation reflects strategic interest and potential operational alignment.

What Zero Actually Is

LayerZero moved ~$70 billion in cross-chain stablecoin volume. The bridge infrastructure proved demand, yet the throughput ceiling of homogeneous validation models became the limiting factor.

Why homogeneous validation hits a ceiling

Why homogeneous validation hits a ceiling: every validator replays the same transactions (Ethereum model).

Ethereum does 20–30 transactions per second. Solana does ~3,000. Both are designed around general-purpose execution and state machine replication. Institutional trading environments operate in microseconds, restrict position visibility, and treat settlement timing as a regulatory parameter rather than a block interval.

Zero represents their attempt to redesign that model.

The Decentralized Multi-Core World Computer

Zero splits responsibilities into two validator classes:

  • Block Producers — powerful nodes executing transactions in parallel “Atomicity Zones,” generating zero-knowledge proofs of execution.

  • Block Validators — lightweight nodes (home computers, phones) that verify proofs instead of re-executing transactions.

This design shifts the bottleneck from re-execution to proof verification and network bandwidth.

Separation of execution and verification

Separation of execution (Block Producers) and verification (Block Validators).

The Technical Foundation

The 2M TPS per zone claim depends on four components working in sync:

  • Storage (QMDB) — a verifiable database architecture claiming 100× faster state writes than Ethereum’s trie structure.

  • Scheduling (FAFO) — a scheduler that runs transactions in parallel within zones.

  • Networking (SVID) — pushes 10 GB/s of block data across the network, necessary when producers publish proofs instead of full blocks.

  • Proving (Jolt Pro) — GPU clusters proving execution correctness at gigahertz scale.

How Zero Differs From Other Scaling Approaches

The 2 million TPS claim is 100,000× Ethereum’s throughput. But context matters.

Monad uses parallel execution with pipelined consensus to reach ~10,000 TPS in a monolithic structure — one validator set, one execution environment.

Celestia decouples data availability from execution entirely. Rollups post data to Celestia for ordering and availability, then execute separately.

Zero introduces heterogeneous execution: multiple zones running different VMs and rule sets, coupled through a shared settlement layer. Producers in each zone execute transactions in parallel and prove correctness via ZK. Validators verify proofs instead of re-executing. All zones share one final settlement layer preventing partitioning.

Zero multi-core design

Zero’s multi-core design: multiple Atomicity Zones settling into one shared consensus/settlement layer.

Proof verification becomes the primary validation path instead of full state re-execution.

Three Specialized Execution Zones

Zero launches with three zones aimed at institutional workflows.

A general-purpose EVM zone for smart contracts and DeFi applications — Ethereum-compatible execution, but parallelized.

A privacy zone for confidential transactions where on-chain data is hidden from the base layer — critical for asset managers and trading firms that cannot broadcast positions.

A trading/settlement zone optimized for matching engines and tokenized securities settlement, where latency and throughput are operational requirements.

The design acknowledges a tradeoff: composability across zones requires bridge logic, so contracts in the EVM zone cannot directly call the trading zone. That constraint appears intentional — institutional users prefer segregated execution environments to reduce surface area and allow zone-specific validator sets.

Zero architecture overview

Zero’s multi-core design: multiple Atomicity Zones settling into one shared consensus/settlement layer

The Institutional Backing

Citadel Securities collaborates on ultra-low-latency infrastructure. ARK Invest is both equity and token investor. DTCC and ICE evaluate suitability for securities settlement and trading. Google Cloud provides infrastructure.

ZRO Tokenomics

ZRO becomes Zero’s native currency for staking and network participation. Supply is fixed at 1 billion, with 80% locked until 2027.

The governance model uses delegated Proof-of-Stake with no slashing. Ethereum and Solana slash validators who misbehave. Zero does not. Validators remain online due to reward structure and governance override mechanisms.

Without slashing, security relies more heavily on incentive alignment and governance response.

What Actually Matters

Zero’s architecture is unusual. Decoupling execution from settlement while coupling heterogeneous zones through shared consensus differs from monolithic parallelization and pure DA-layer approaches.

Architectural novelty does not guarantee demand.

If institutions require 10,000 TPS and sub-second finality, alternatives already exist. If they require cheaper data availability, DA layers already solve that. If they require privacy, specialized chains exist.

Zero’s bet is that institutional finance needs segregated execution zones under unified settlement.

Adoption will determine whether zoning solves operational constraints or introduces structural complexity.

Links

Website
Documents
X / Twitter

HighTower Research