TaifoonTAIFOON
[ Intel · The Traversal Orbit ]

The golden traversal

Two 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.

Mayan
Decode completeness

Receipts are flowing on the resurrected pipeline; this protocol’s event decoders are the next stage. The meter moves when real orders decode, never before.

Genome stream · live
Live · streaming via SSEAwaiting first indexed fill
Waiting for first SSE event. Source: /api/intel/genomes/stream/mayan

curl -N https://www.taifoon.io/api/intel/genomes/stream?protocol=mayan

LayerZero V2GOLDmessaging
Decode completeness

Receipts are flowing on the resurrected pipeline; this protocol’s event decoders are the next stage. The meter moves when real orders decode, never before.

The decode ledger · what closes the gap
  • · Implement fill-side decoder: PacketReceived event on destination chain
  • · DVN signer enumeration per oapp
Genome stream · live
Live · streaming via SSEAwaiting first indexed fill
Waiting for first SSE event. Source: /api/intel/genomes/stream/layerzero

curl -N https://www.taifoon.io/api/intel/genomes/stream?protocol=layerzero

[ The Robinhood lane · already under the root ]
BLOCKS PROOF-ANCHORED
5,569,021
MMR TWIGS
2,719
LIVE HEAD
48,181,002
PROVABLE NOW
YES · /api/v5/verifiable/4663

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 62chains. A venue’s volume becomes provable the day its chain is under the root; this one already is.

[ The filtered stream · pick a protocol ]

One live wire, filterable by protocol: the relay filters server-side, so a subscriber pays only for the genomes it cares about. The pinned chips publish in production today; the registry chips are the catalog the decoders walk next.

TAPE IDLE · RECONNECTING
the spine pulse lands within ~10s of connecting
[ The translation · what agents subscribe to ]
The live wire format
{
  "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
}
Why it sells

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 Moonbeam bridge indexer publishes BridgeOut and Delivered genomes into this exact stream, decoded from mainnet logs and notified to every subscriber.