WareBenchPropose a projectENIT

PRODUCTS / RESEARCH

Zephyr Chain

Experimental blockchain and proof-verification research. This is a research project, not a claim of production readiness.

View public repository →All products →

Project overview

Experimental blockchain and proof-verification research. This is a research project, not a claim of production readiness.

For shipped features, installation requirements, version and license, consult the latest documentation in the public repository.

Contact WareBench →
SECTION 01

Documented capabilities

Capabilities and tools described in the public project documentation.

What the software does

  • Explores proof-carrying transactions, Sparse Merkle state and deterministic execution in experimental Protocol v2.
  • Implements and tests foundations for quorum-certificate consensus, cross-shard receipts, lightweight verification and token policy.
  • Includes development-only observer and local test/benchmark tools; the research targets both high throughput and low-resource verification.

Source and latest documentation ↗

SECTION 02

Architecture and integrations

Experimental protocol foundations: identities and genesis → proof-oriented object state → consensus certificates → verifiable receipts.

Architecture overview

Experimental protocol foundations: identities and genesis
proof-oriented object state
consensus certificates
verifiable receipts.

Source and latest documentation ↗

SECTION 03

Requirements and getting started

Consult docs/protocol-v2.md and docs/protocol-v2-implementation-status.md for implemented boundaries. The repository documents local quick/full correctness checks via scripts/verify-v2.sh.

Prerequisites

Go toolchainProtocol v2 documentationLocal verification tools

Quick start

  1. 1Read Protocol v2 and implementation-status documents.
  2. 2Run the documented scripts/verify-v2.sh quick checks.
  3. 3Review the full correctness gate before larger tests.
SECTION 04

Limitations and operating boundaries

No independently audited multi-operator public production mainnet is claimed. One-million TPS is an aspirational benchmark target, not measured production capacity. The observer is not a mainnet validator.

Key boundaries

Research status

No independently audited multi-operator public production mainnet is claimed.

Performance target

One-million TPS is an aspirational benchmark target, not measured production capacity.

Observer role

The observer is not a mainnet validator.

Source and latest documentation ↗