The Coordination Layer, in One Page
Everyone works. Nothing works together.
A chain, an agent framework, a workflow platform, a cloud runtime: each keeps its own clock, its own logs and its own idea of what happened. Work crosses all of them every day. An agent is hired on one chain, does the job on another, and gets paid on a third. The record of that work stays home, split into private logs that nobody else can check.
Every link between two of these islands is custom software both sides trust blind. On chains it is called a bridge; everywhere else it is called an integration. At 61 chains the pairs alone are 1,830 routes, and each one is somebody's plumbing project.
The coordination layer is the other approach: instead of wiring every pair, every island commits to one shared record, and anyone checks against that.
How the record is built
Collect. Our collectors, the spinners, read block headers from 61 chains around the clock: Ethereum, the OP Stack and Arbitrum families, Solana, Bitcoin, Polkadot parachains, Robinhood Chain and more.
Commit. Each chain's headers go into its own append-only tree, 2,048 blocks at a time. We call each bundle a twig.
Fold. Every ten seconds the roots of all 61 trees fold into one value, the superroot.
Prove. If a block is under the root, there is a short path of hashes from that block up to it. A full V5 proof carries six layers: the superroot, the chain header, the path from chain to root, the path from block to chain, the event itself when there is one, and a finality commitment that says why that block cannot be undone on its own chain. Finality is typed per chain: an Ethereum checkpoint, an OP Stack output root, Solana's tower consensus, a GRANDPA justification on Polkadot, or confirmation depth on chains without a finality gadget.
Anyone can recompute every step from public chain data. That is the point: a claim that something happened stops depending on who is making it.
Read and write
The layer speaks two verbs.
Read is the commons. The root and its proofs are free and keyless. This is live today at taifoon.io/v1.
Write is the economy. Writing means committing something into the record: chain headers and decoded protocol events today; signed envelopes from off-chain platforms, job declarations and attestations next. Writes are namespaced and bonded, because a claim with money behind it is a claim worth checking. Those last three are proposed, and we label them that way everywhere.
Every event is also written as one fixed-length string, the genome: T:EPOCH/ENTITY:ID/ACTION:CHAIN:REF. A swap, a filled order, an agent detection and a block ingest all read the same way, whichever island they came from.
Check it yourself
- The live root and the chains inside it: taifoon.io/v1/root
- A real proof, one Ethereum block to the root: taifoon.io/v1/root/proof/1/26067000
- The status page: taifoon.io/status
- The API: taifoon.io/docs/api
What is not done yet
Today one party computes the root, and anyone can recheck it. Spreading that computing across independent operators, each posting a bond behind what they read, is the next step. It is the one layer this company is being built to decentralize.