TaifoonTAIFOON
← every chain
[ RPC · chain 1 ]

Ethereum, with proofs.

JSON-RPC for Ethereum through one gateway over 8 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/1 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
HTTPS
https://coord.taifoon.dev/gw/rpc/1
methods
eth_blockNumber · eth_call · eth_getLogs · eth_getBlockBy* · eth_getTransaction* · eth_chainId · batch ≤ 20 · taifoon_getProof
health
healthy · 8 endpoints, 7 for logs read 2026-10-16 17:14 UTC
measured
best upstream 83 ms average, 151 ms p95, 88 % success · 8 active endpoints, archive available (the rotation's own probe, 2026-10-16 17:13 UTC) read 2026-10-16 17:14 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 Ethereum

The producer follows these protocols on Ethereum: layerzero_v2 · taifoon_assurance · u_demo_counter. 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-ethereum","name":"My Ethereum watch","protocols":["layerzero_v2"],"filters":{"chains":[1]}}'
curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-ethereum&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 Ethereum: Across Protocol V3 DepositSource 0x5c7BCd6E7De5423a257D81B442095A1a6ced35C5 · Across Protocol V3 FillTarget 0x5c7BCd6E7De5423a257D81B442095A1a6ced35C5 · deBridge DLN DepositSource 0xeF4fB24aD0916217251F553c0596F8Edc630EB66 · deBridge DLN ClaimSource 0xeF4fB24aD0916217251F553c0596F8Edc630EB66 · deBridge DLN FillTarget 0xE7351Fd770A37282b91D153Ee690B63579D6dd7f · deBridge DLN BridgeGate 0x43dE2d77BF8027e25dBD179B491e8d64f38398aA and 41 more.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain
chain
Ethereum (1)
transaction
0xa8a1dcd6e0f64a688dbdd8cdf7d29e71af37680af486f1fe23a2689c6134f205
block
26206512
time
2026-10-16 17:12 UTC
protocol
layerzero_v2
2 · typed transition
order key
layerzero_v2:0x450221b62dea1340e7982f8fbf771d0745186e05700af80bc3c97d09ebd456ca
stage
→ Placed
lifecycle
Created
stages
Placed · Verified · Committed · Filled · Failed
3 · envelope in the pipe
kind
observe
catalogue row
observe:collect:order:observe
schema
taifoon.order.v1
leaf
0x8214cd141802e020b38ee303494ab564e30de8a4d219c71939ff290d196d4eb3
pipe seq
243024
signer
the key’s actor: its session key, certified by its own wallet

From the layerzero-messages board. The same step is streamed to keyed subscribers as an envelope and proven under the superroot.

[ Proof streaming ]

Checked under the superroot

The order above, read through the proof op: its leaves verify under the superroot. read 2026-10-16 17:14 UTC

curl -s https://coord.taifoon.dev/v1/protocol/layerzero_v2/order/0x450221b62dea1340e7982f8fbf771d0745186e05700af80bc3c97d09ebd456ca
[ Pricing ]

Free to start, metered after

unitfree a day (key / visitor)USDC per 1MGRID per 1M
one JSON-RPC request (a batch of up to 20 calls is one request)1000 / 1000.50000025
one request that returns a block proof (taifoon_getProof, or any request sent with x-taifoon-proof: 1)0 / 05.000000250

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

[ Partnership ]

Run Ethereum 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:1

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