[ RPC · chain 324 ]

zksync, with proofs.

JSON-RPC for zksync 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/324 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

HTTPS: https://coord.taifoon.dev/gw/rpc/324
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 139 ms average, 151 ms p95, 99.7 % 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 zksync

The producer follows these protocols on zksync: u_demo_counter · u_taifoon_bridge_arc · u_taifoon_bridge_base · u_taifoon_ticp_claim_arc · u_taifoon_ticp_claim_base · u_taifoon_ticp_claim_robinhood · u_taifoon_ticp_gate_arc · u_taifoon_ticp_gate_base · u_taifoon_ticp_gate_robinhood · u_taifoon_trn_surge_arbitrum · u_taifoon_trn_surge_arc · u_taifoon_trn_surge_base · u_taifoon_trn_surge_robinhood · u_taifoon_vaults_robinhood. 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-zksync","name":"My zksync watch","protocols":["u_demo_counter"],"filters":{"chains":[324]}}'

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

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

Protocol contracts the producer knows on zksync: Across Protocol V3 DepositSource 0xe0B015E54d54fc84a6cB9B666099c46adE9335FF · Across Protocol V3 FillTarget 0xe0B015E54d54fc84a6cB9B666099c46adE9335FF · Relay.link DepositSource 0x4cd00e387622c35bddb9b4c962c136462338bc31 · Symbiosis DepositSource 0x38307CB291Af47Af9847c134a34E9477c939Ca28 · Orbiter Finance DepositSource 0x4C4AF8DBc524681930a27b2F1Af5bcC8062E6fB7 · Orbiter Finance FillTarget 0x4C4AF8DBc524681930a27b2F1Af5bcC8062E6fB7 and 1 more.

[ Per-contract events ]

An event, as the lambda sees it

No order step on zksync 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 zksync 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:324

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