QUAD - the whole stack in one read

The four jobs

Each chain owns a different job, and they don't blur into each other.

Core holds value

The careful accounting layer — chain state, fees, validators, custody, and what's admitted.

Infra proves work

Store, prove, retrieve, and remember — paid in BIGHT, with receipts. Available through Infra-owned quote-first routes.

Bridge carries across

Move assets and proofs between chains, with a record of what crossed.

Liquid moves fast

Fast trading and settlement, built so speed never becomes final truth.

Coordinated, not merged

They help each other, but they never become one thing.

Evidence can cross between the chains — a receipt, a proof, a route — but each chain decides for itself what that evidence means under its own rules. Nothing gets forced on anyone.

And each chain except Core runs as two cooperating programs, not one. Here's why that's safer. The full map is on architecture.

Where each part is up to

One compact status read. The current numbers live on each chain's own pages.

CoreLive and observable.

InfraLive owner surface — verify the current buy, store, proof, and retrieval routes before use.

BridgeLive with real evidence; public movement gated.

LiquidLive chain, producing blocks; trading closed.

EconomicsThe opening path is published; the lanes stay gated.

No catchNo sale, airdrop, or reward.

What each part is for

Useful paths stay attached to the chain that owns the receipt.

ChainUse it toBut not for

CoreCheck value, watch validators, read supply and custody state.Not a wallet, sale, airdrop, claim, or price page.

InfraStore and prove data, retrieve it, and keep receipts.Not compute rewards, node-earning, or open access to private files.

BridgeMove between chains, and read pools, vaults, and host evidence.Not destination admission, a swap desk, or open movement by default.

LiquidFast motion, positions, risk, and settlement requests.Not live markets, leverage, or Core value by speed alone.

Why keeping them separate matters

Most things go wrong when one chain borrows meaning from another.

A receipt isn't truth

It proves a bounded event on the chain that owns it — it doesn't force every other chain to agree.

Delivery isn't admission

Bridge can carry evidence to a door; the receiver still decides what to let in, under its own rules.

Speed isn't worth

Liquid can move quickly, but the final balance belongs to whatever owns settlement.

Being visible isn't being launched

Public pages, status files, and summaries help you review. They don't open the economics.

How it grows

Each part moves forward only when public proof can carry the claim.

Show it

Publish state, metadata, public pages, and safe first-read paths.

Harden it

Run repeatable endpoint, product, failure, and release checks.

Explain it

Publish purpose, model, risks, limits, and boundaries.

Freeze it

Lock the intended genesis, metadata, endpoints, and route contracts.

Open one lane

Open a single bounded lane with published status, fee, receipt, and recovery labels.

Expand on proof

Broader movement and market language wait for stronger receipts and dated updates.