[ RPC · chain 42161 ]

Arbitrum One, with proofs.

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

HTTPS: https://coord.taifoon.dev/gw/rpc/42161
methods: eth_blockNumber · eth_call · eth_getLogs · eth_getBlockBy* · eth_getTransaction* · eth_chainId · batch ≤ 20 · taifoon_getProof
health: healthy · 6 endpoints, 3 for logs read 2026-10-16 17:14 UTC
measured: best upstream 54 ms average, 75 ms p95, 99.5 % success · 6 active endpoints, archive available (the rotation's own probe, 2026-10-16 17:12 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 Arbitrum One

The producer follows these protocols on Arbitrum One: 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-arbitrum-one","name":"My Arbitrum One watch","protocols":["layerzero_v2"],"filters":{"chains":[42161]}}'

curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-arbitrum-one&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 Arbitrum One: Across Protocol V3 DepositSource 0xe35e9842fceaCA96570B734083f4a58e8F7C5f2A · Across Protocol V3 FillTarget 0xe35e9842fceaCA96570B734083f4a58e8F7C5f2A · deBridge DLN DepositSource 0xeF4fB24aD0916217251F553c0596F8Edc630EB66 · deBridge DLN ClaimSource 0xeF4fB24aD0916217251F553c0596F8Edc630EB66 · deBridge DLN FillTarget 0xE7351Fd770A37282b91D153Ee690B63579D6dd7f · deBridge DLN BridgeGate 0x43dE2d77BF8027e25dBD179B491e8d64f38398aA and 35 more.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain

chain: Arbitrum One (42161)
transaction: 0x3586a92eef134e7e5f5413b41c90a24aca291e1b0b218226fde777147295a0ac
block: 515437975
time: 2026-10-16 17:12 UTC
protocol: layerzero_v2

2 · typed transition

order key: layerzero_v2:0xb8bb7e6025410d49ee99cc52dabe38d13d6f557b2e144650df22a5e12967c53c
stage: → 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: 0xf143ecc6233685ab57457a7569fa92fcbbfd5312aa148e310cbe1a037161adc6
pipe seq: 243032
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/0xb8bb7e6025410d49ee99cc52dabe38d13d6f557b2e144650df22a5e12967c53c

[ 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 Arbitrum One 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:42161

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