[ RPC · chain 8453 ]

Base, with proofs.

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

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

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

curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-base&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 Base: Across Protocol V3 DepositSource 0x09aea4b2242abC8bb4BB78D537A67a245A7bEC64 · Across Protocol V3 FillTarget 0x09aea4b2242abC8bb4BB78D537A67a245A7bEC64 · deBridge DLN DepositSource 0xeF4fB24aD0916217251F553c0596F8Edc630EB66 · deBridge DLN ClaimSource 0xeF4fB24aD0916217251F553c0596F8Edc630EB66 · deBridge DLN FillTarget 0xE7351Fd770A37282b91D153Ee690B63579D6dd7f · deBridge DLN BridgeGate 0xc1656B63D9EEBa6d114f6bE19565177893e5bCBF and 34 more.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain

chain: Base (8453)
transaction: 0x1caff15986049427d057da5d4720842490252c3a76345faf6ce22d0265db92ba
block: 52690705
time: 2026-10-16 17:12 UTC
protocol: layerzero_v2

2 · typed transition

order key: layerzero_v2:0xf3be8c0030d448f7f3b347a82db929766561fce5525e4316248a1ba06d730878
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: 0xae83daea14c3c9d47f63070f7739645d8276c6424d0db574bb950376de4cd16f
pipe seq: 243031
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/0xf3be8c0030d448f7f3b347a82db929766561fce5525e4316248a1ba06d730878

[ 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 Base 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:8453

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