EPOCH
HEAD/ 512
LITcells
DARKunclaimed
ROOT
SETTLING
THE COORDINATION LAYER // 62 CHAINS // ONE ROOT

Sixty-two chains agree
every ten seconds.

Nothing makes them. They have no shared clock, no shared validator set and no knowledge of each other. A swarm of independent operators reads all of them, stakes on what it saw, and folds the result into a single value that anyone can check. That single value is the coordination.

THE SETTLE PULSE ABOVE IS ONE EPOCH
01 // WHAT THE FIELD DOES

Don't take the root on trust. Check one.

Paste a transaction, an address, a block or a chain. The same box answers all four, because underneath they are the same question asked at different heights of the stack. Every endpoint below is real — the panel shows the shape of the answer; live results come from api.taifoon.dev.

/VERIFY
Transaction Address Chain Block
A PROOF IS 17 HASHES · A CHECK IS ONE CONTRACT CALL · READING IS FREE

02 // WHY IT WORKS

Sixty-two chains go in.
One value comes out.

Every chain is aggregated into a per-chain root, and every per-chain root folds into a single superroot, recomputed every ten seconds and anchored on Base.

coordination = the point where n independent parties must converge on one value

Below that point nobody needs to agree with anybody — a root is a function of headers, and two honest machines compute the same one. Above it, every consumer inherits the same value. They are coordinated by construction, because there is nothing else to be coordinated on.

See the whole stack at 100 feet →

And one layer is still ours alone.

Today that single value is computed by one indexer on a ten-second timer. Everything beneath it is independently checkable; everything above it inherits whatever that one process decided.

today: computed
the lattice: agreed

The lattice is 512 cells — 64 chain slots by 8 lanes — where a quorum attests each root, anyone can challenge one, and a wrong attestation costs a bond. It is the one part of this system that is modelled rather than shipped, and we would rather say so than colour it green.

Read the model →

03 // THE PRIVATE NETWORK

Four levels, and what each one actually proves

Run your own spinner, your own agents, your own containers — on the same metal as a 62-chain proof spine, so verified chain state is a local mount rather than a queue of RPC calls. Every level below states what it does not prove. That column is the one most confidential-compute pages leave out, and it is the one that matters when something goes wrong.

PUBLIC

Shared spinners, public results. You read the same superroot as everyone else and pay per query. Nothing of yours runs here.

Proves
inclusion against the anchored root
Does not prove
anything about who asked, or when
Meter
per query · reads free

ISOLATED

Your own spinner instance, your IP, your chain set. Dedicated storage and a private endpoint. Ordinary hardware — the boundary is operational, not cryptographic.

Proves
tenancy separation · your own chain selection
Does not prove
that the host cannot read memory
Meter
$/chain-mo + modules

ENCLAVED

The workload runs in an Intel TDX confidential VM. The image is measured, the measurement is attested, and the attestation is published so a client can refuse to talk to an unexpected build.

Proves
which image is running, to a remote party
Does not prove
that the image behaves as described — attestation binds code, never conduct
Meter
$/CVM-hr + modules

SEALED

Enclave plus GPU confidential compute over protected PCIe, one GPU bound to one CVM. Keys are generated inside and never leave. Signing runs through a policy vault; every signature lands in an append-only log whose root is anchored.

Proves
keys never left · every signature is logged and anchored
Does not prove
determinism — GPU inference is not batch-invariant and will not replay bit-for-bit
Meter
$/GPU-hr + $/signature

One honest note we will keep making: an attestation tells you what code is running, not that the code is honest, and a hash of an output is not a proof the output was right. Everything at SEALED is designed around that limit rather than around hiding it — which is why signatures go to an anchored log instead of a promise.

04 // MOUNTED, NOT INTEGRATED

Chain state as a local mount

On a general cloud your agent spends half its budget and most of its latency on RPC and indexers. Here it is a filesystem away.

ModuleWhat it isMeter
chain.headerscanonical headers on all 62 chains — no RPC juggling$/1k reads
chain.finality“is this final?” as one call — GRANDPA, BoLD, PoS checkpoints, output roots$/query
chain.superrootcurrent superroot + per-chain breakdownfree with hosting
chain.proofsV5 blobs, transaction and event proofs, receipts$/proof
chain.eventsdecoded protocol events as a stream$/1k events
chain.intelthe search, as an API — intel query and entity resolveper query
storage.wormappend-only audit log, hash-chained, root anchored$/GB-mo
vaultcustody by policy — workloads request signatures, never keys$/signature
inferenceGPU lane, mountable inside a sealed CVM$/M tokens
05 // FOUR WAYS IN

Ordered by how much you have to trust

Nobody should start at the bottom. Each door is a larger commitment than the last, justified by the previous one having worked.

TAIFOON // APPEND-ONLY BELOW · ATTESTED ABOVE
READING IS FREE · TRUST IS OPTIONAL