[ RPC · chain 167000 ]

taiko, with proofs.

JSON-RPC for taiko through one gateway over 2 measured endpoints. Every answer carries a receipt; a proved read adds the block proof under the superroot.

[ Endpoints ]

Call it now

curl -s https://coord.taifoon.dev/gw/rpc/167000 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

HTTPS: https://coord.taifoon.dev/gw/rpc/167000
methods: eth_blockNumber · eth_call · eth_getLogs · eth_getBlockBy* · eth_getTransaction* · eth_chainId · batch ≤ 20 · taifoon_getProof
health: healthy · 2 endpoints, 1 for logs read 2026-10-18 16:48 UTC
measured: best upstream 135 ms average, 142 ms p95, 99.9 % success · 2 active endpoints, archive available (the rotation's own probe, 2026-10-18 16:48 UTC) read 2026-10-18 16:48 UTC

Writes: transaction sends are being added through the streaming settle path; until then eth_sendRawTransaction is refused with a named reason. Limits and prices: below.

[ Agents ]

Quick MCP

Connect an agent to the layer in one line. The MCP server answers without a key; its taifoon_register tool issues one.

claude mcp add --transport http taifoon https://coord.taifoon.dev/mcp

First call from any MCP client: tools/list, then taifoon_proof_tx with a chain and a transaction hash.

[ Data subscriptions ]

Stream what happens on taiko

The producer follows this protocol on taiko: layerzero_v2. Register a project scoped to the chain, then stream it or take its webhook.

curl -s -X POST https://coord.taifoon.dev/v1/projects -H "X-API-Key: $KEY" -H 'content-type: application/json' -d '{"id":"my-taiko","name":"My taiko watch","protocols":["layerzero_v2"],"filters":{"chains":[167000]}}'

curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-taiko&from_seq=0" -H "X-API-Key: $KEY"

curl -s https://coord.taifoon.dev/v1/protocol/layerzero_v2/stuck

Protocol contracts the producer knows on taiko: Relay.link DepositSource 0x4cd00e387622c35bddb9b4c962c136462338bc31 · LayerZero V2 DepositSource 0x1a44076050125825900e736c501f859c50fE728c · Hyperlane DepositSource 0xeA87ae93Fa0019a82A727bfd3eBd1cFCa8f64f1D · Meson Finance DepositSource 0x25ab3efd52e6470681ce037cd546dc60726948d3 · Symbiosis DepositSource 0x292fC50e4eB66C3f6514b9E402dBc25961824D62 · Rango Exchange DepositSource 0x69460570c93f9DE5E2edbC3052bf10125f0Ca22d.

[ Per-contract events ]

An event, as the lambda sees it

No order step on taiko was in the boards at this read. read 2026-10-18 16:48 UTC

[ Proof streaming ]

Checked under the superroot

A proved read on any request: send x-taifoon-proof: 1 with the call, or taifoon_getProof.

[ Pricing ]

Free to start, metered after

unit	free a day (key / visitor)	USDC per 1M	GRID per 1M
one JSON-RPC request (a batch of up to 20 calls is one request)	1000 / 100	0.500000	25
one request that returns a block proof (taifoon_getProof, or any request sent with x-taifoon-proof: 1)	0 / 0	5.000000	250

One key and one balance for every product. Plans and top-ups: pricing. read 2026-10-18 16:48 UTC

[ Partnership ]

Run taiko with Taifoon

A chain or protocol team can claim the owner seat of its record: it then maintains its lanes and stage table, sets its pricing share, and the Conclave records the ownership and the share. Endpoint operators can add capacity to the rotation and earn per call.

curl -s https://coord.taifoon.dev/v1/owners/chain:167000

Claim: POST https://coord.taifoon.dev/v1/owners/chain:167000/claim with your key and a signature from an address your contracts name. Partner cards · add capacity.