[ RPC · chain 43114 ]

Avalanche C-Chain, with proofs.

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

HTTPS: https://coord.taifoon.dev/gw/rpc/43114
methods: eth_blockNumber · eth_call · eth_getLogs · eth_getBlockBy* · eth_getTransaction* · eth_chainId · batch ≤ 20 · taifoon_getProof
health: healthy · 3 endpoints, 1 for logs read 2026-10-16 15:44 UTC
measured: best upstream 52 ms average, 67 ms p95, 100 % success · 3 active endpoints, archive available (the rotation's own probe, 2026-10-16 15:43 UTC) read 2026-10-16 15:44 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 Avalanche C-Chain

The producer follows these protocols on Avalanche C-Chain: layerzero_v2 · 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-avalanche-c-chain","name":"My Avalanche C-Chain watch","protocols":["layerzero_v2"],"filters":{"chains":[43114]}}'

curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-avalanche-c-chain&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 Avalanche C-Chain: deBridge DLN DepositSource 0xeF4fB24aD0916217251F553c0596F8Edc630EB66 · deBridge DLN ClaimSource 0xeF4fB24aD0916217251F553c0596F8Edc630EB66 · deBridge DLN FillTarget 0xE7351Fd770A37282b91D153Ee690B63579D6dd7f · deBridge DLN BridgeGate 0x43dE2d77BF8027e25dBD179B491e8d64f38398aA · Mayan Finance (Swift) DepositSource 0x337685fdab40d39bd02028545a4ffa7d287cc3e2 · Mayan Finance (Swift) FillTarget 0xd78d199f8c402e7b5cc2abe278df0412400a3bae and 24 more.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain

chain: Avalanche C-Chain (43114)
transaction: 0x982d7a477902f96895b3f05c6c2f679c8dff98dce7e77f04ebfb14726fe6872c
block: 97719004
time: 2026-10-16 15:42 UTC
protocol: layerzero_v2

2 · typed transition

order key: layerzero_v2:0x622065d8f8b889ef1f968a0d35339dc61e040eacfffed5ca740615e6f66bc24a
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: 0xdb1367412e93e1f290e73f3e717b04d4a824981c0eb276935cf27050ca556f6c
pipe seq: 239710
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 15:44 UTC

curl -s https://coord.taifoon.dev/v1/protocol/layerzero_v2/order/0x622065d8f8b889ef1f968a0d35339dc61e040eacfffed5ca740615e6f66bc24a

[ 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 15:44 UTC

[ Partnership ]

Run Avalanche C-Chain 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:43114

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