Network interchain

Remote facts, locally checked

Do not trust the bridge. Verify the history it speaks for.

An interchain operation begins with a light client: a local verifier for a remote chain’s finality and state commitment. Settlement follows only when the claimed fact appears inside the proof’s public meaning.

01

The verifier cabinet

Several chains, no universal trust shortcut.

implemented

Dregg whole-history client

Verifies and folds finalized dregg history into an anchored head.

implemented

Tendermint and ICS-23

Checks consensus headers, membership proofs, and Cosmos bank facts against committed roots.

implemented

Solana and EVM settlement verifiers

Verifier programs and contracts check the corresponding proof envelopes and public lanes.

development

Relayers and feeds

Evidence-source and relayer code exists; this is not a production generalized bridge service.

02

A real settlement

Base Sepolia contains one verified fixture history.

On 13 July 2026, the settlement contract verified a real Groth16 proof on Base Sepolia and advanced its recorded dregg history to height two.

Chain
Base Sepolia · 84532
Proven height
2
Gas
604,789
Transaction
0xbd2cac…e963b

03

The refusal is the feature

No outbound message root enters by operator assertion.

The settlement proof does not yet expose an outbound message root. The contract therefore rejects every nonzero root, and its proof-membership query always returns false. Hyperlane- and LayerZero-shaped adapters remain inert until a new proof lane binds the message root.

proofHistory lanesbound
contractContinuity + verifierchecked
message rootOutbound adapterrefused