[ RPC · chain 42220 ]

Celo, with proofs.

JSON-RPC for Celo through one gateway over 4 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/42220 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

HTTPS: https://coord.taifoon.dev/gw/rpc/42220
methods: eth_blockNumber · eth_call · eth_getLogs · eth_getBlockBy* · eth_getTransaction* · eth_chainId · batch ≤ 20 · taifoon_getProof
health: healthy · 4 endpoints, 3 for logs read 2026-10-16 17:14 UTC
measured: best upstream 123 ms average, 192 ms p95, 100 % success · 4 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 Celo

The producer follows these protocols on Celo: layerzero_v2 · 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-celo","name":"My Celo watch","protocols":["layerzero_v2"],"filters":{"chains":[42220]}}'

curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-celo&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 Celo: Across Protocol V3 DepositSource 0x3baD7AD0728f9917d1Bf08af5782dCbD516cDd96 · Across Protocol V3 DepositSource 0x09aea4b2242abC8bb4BB78D537A67a245A7bEC64 · Across Protocol V3 FillTarget 0x3baD7AD0728f9917d1Bf08af5782dCbD516cDd96 · Across Protocol V3 FillTarget 0x09aea4b2242abC8bb4BB78D537A67a245A7bEC64 · Relay.link DepositSource 0x4cd00e387622c35bddb9b4c962c136462338bc31 · Li.Fi / Jumper DepositSource 0x1231DEB6f5749EF6cE6943a275A1D3E7486F4EaE and 7 more.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain

chain: Celo (42220)
transaction: 0xc5b969c9fba89bc055124d6d4ddc73c4fc2a29781b2ba7542a96f6f28dbb7f5a
block: 80269877
time: 2026-10-16 17:11 UTC
protocol: layerzero_v2

2 · typed transition

order key: layerzero_v2:0x87b81985ea4eea1163b7ec334b0e22e8110a188f4339c007cd0e88eef381e922
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: 0xfcbea93389b423fc90ed681e787bdaea97e41a755534d9c8e4bb909c1c0e98fd
pipe seq: 242945
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/0x87b81985ea4eea1163b7ec334b0e22e8110a188f4339c007cd0e88eef381e922

[ 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-16 17:14 UTC

[ Partnership ]

Run Celo 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:42220

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