The golden traversal
Three golden protocols traversed side by side on the live spine. Any event on any covered architecture becomes a genome an agent can read; every claim on this page is live from the running system or honestly absent.
TWO INSTRUMENTS: order counts come from decoded order flow. The decode meter measures event-level ABI coverage on watched contracts. Different measurements, both live, never combined.
SOURCE UNREACHABLE at render: the live overview could not be read, so this meter shows nothing rather than a substitute.
SOURCE UNREACHABLE at render: the live rollup could not be read. Unreachable is not zero; this pane never substitutes a number.
curl -N https://www.taifoon.io/api/intel/genomes/stream?protocol=mayan
SOURCE UNREACHABLE at render: the live overview could not be read, so this meter shows nothing rather than a substitute.
SOURCE UNREACHABLE at render: the live rollup could not be read. Unreachable is not zero; this pane never substitutes a number.
curl -N https://www.taifoon.io/api/intel/genomes/stream?protocol=layerzero
SOURCE UNREACHABLE at render: the live overview could not be read, so this meter shows nothing rather than a substitute.
SOURCE UNREACHABLE at render: the live rollup could not be read. Unreachable is not zero; this pane never substitutes a number.
curl -N https://www.taifoon.io/api/intel/genomes/stream?protocol=orbiter_finance
Robinhood Chain (4663) is fully inside the spine today: every block above is proof-anchored, and any transaction on it resolves to the same root as 68chains. A venue’s volume becomes provable the day its chain is under the root; this one already is. The inbound-orders count reads exact hourly buckets that began accumulating on 2026-08-28: a young window under-reports, never over.
- across10,107
- lifi8,654
- debridge211
Orders decoded into chain 4663 in the last 24h, counted per routing protocol. A protocol absent here routed nothing we decoded in the window.
Decoded orders in the last 24h, exact hourly buckets, one figure per protocol. Protocols absent here have no decoded orders in the window yet; nothing is padded.
One live wire, filterable by protocol: the relay filters server-side, so a subscriber pays only for the genomes it cares about. Each chip is a protocol in the synced registry; the ones with decoded flow are publishing into this stream right now.
{
"genome_id": "keccak(chain·block·tx·log·slug)",
"ts": 1787909761751,
"protocol_slug": "your-protocol",
"event_kind": "BridgeOut | Delivered | OrderCreated | …",
"src_chain_id": 1284,
"dst_chain_id": 8453,
"src_tx": "0x…",
"amount_raw": "2500000000000000000",
"solver": "0x…",
"latency_ms": 12400,
"finality_type_id": 7
}Every event your protocol emits, on every architecture it touches, arrives as one deterministic record: source, destination, amount, solver, latency, finality type, and an id that binds it to a block under the root. Agents do not parse your ABI; they subscribe to your genome. The reference integration runs in production today: the protocol decoders publish deposit and fill genomes into this exact stream, decoded from mainnet logs and notified to every subscriber.