[ RPC · chain 36927 ]

Taifoon devnet, with proofs.

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

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

No protocol lane runs on Taifoon devnet yet. A protocol or chain owner can add one as a stream spec: stream services.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain

chain: Taifoon devnet (36927)
transaction: 0xdcd1cc76e91c77039877d34ed7ccd8b150cc2dbb3d966572fc26cdeb6b319463
block: 1856983
time: 2026-10-15 12:03 UTC
protocol: u_demo_counter

2 · typed transition

order key: u_demo_counter:36927:21
stage: → Placed
lifecycle: Funded
stages: Placed · Filled

3 · envelope in the pipe

kind: observe
catalogue row: observe:collect:order:observe
schema: taifoon.order.v1
leaf: 0x7497ad358a717d41277c5fab90a42e317e25bbf929f648f2259a34dae480e534
pipe seq: 30
signer: the key’s actor: its session key, certified by its own wallet

From the demo-counter 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/u_demo_counter/order/36927:21

[ 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 Taifoon devnet 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:36927

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