TaifoonTAIFOON
SIGN IN
← every chain
[ RPC · chain 2222 ]

kava, with proofs.

JSON-RPC for kava through one gateway over 3 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/2222 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
HTTPS
https://coord.taifoon.dev/gw/rpc/2222
methods
eth_blockNumber · eth_call · eth_getLogs · eth_getBlockBy* · eth_getTransaction* · eth_chainId · batch ≤ 20 · taifoon_getProof
health
healthy · 3 endpoints, 2 for logs read 2026-10-18 18:27 UTC
measured
best upstream 57 ms average, 81 ms p95, 87.1 % success · 3 active endpoints (the rotation's own probe, 2026-10-18 18:26 UTC) read 2026-10-18 18:27 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 kava

The producer follows this protocol on kava: 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-kava","name":"My kava watch","protocols":["layerzero_v2"],"filters":{"chains":[2222]}}'
curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-kava&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 kava: Stargate V2 DepositSource 0x45A01E4e04F14f7A4a6702c74187c5F6222033cd · Squid Router DepositSource 0xce16F69375520ab01377ce7B88f5BA8C48F8D666 · LayerZero V2 DepositSource 0x1a44076050125825900e736c501f859c50fE728c · Axelar GMP DepositSource 0xe432150cce91c13a887f7D836923d5597adD8E31 · Meson Finance DepositSource 0x25ab3efd52e6470681ce037cd546dc60726948d3 · Symbiosis DepositSource 0x292fC50e4eB66C3f6514b9E402dBc25961824D62 and 1 more.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain
chain
kava (2222)
transaction
0x920989b73f04241020debc6980e41c2411783746cfb4421afab2940bf1452b67
block
23085169
time
2026-10-18 18:24 UTC
protocol
layerzero_v2
2 · typed transition
order key
layerzero_v2:0x65aee141bd143f4fe1a041294b627440a7aee2ac450f16d408a028bec97d0af0
stage
Placed → Verified
lifecycle
Submitted
stages
Placed · Verified · Committed · Filled · Failed
3 · envelope in the pipe
kind
observe
catalogue row
observe:collect:order:observe
schema
taifoon.order.v1
leaf
0xdb99061d204e42af6639878ee65525d747eb128e6ac9c039c500c667d372a98f
pipe seq
316334
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: the check does not verify (no reason given). read 2026-10-18 18:27 UTC

curl -s https://coord.taifoon.dev/v1/protocol/layerzero_v2/order/0x65aee141bd143f4fe1a041294b627440a7aee2ac450f16d408a028bec97d0af0
[ 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-18 18:27 UTC

[ Partnership ]

Run kava 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:2222

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