[ RPC · chain 2741 ]

abstract, with proofs.

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

HTTPS: https://coord.taifoon.dev/gw/rpc/2741
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 43 ms average, 51 ms p95, 100 % success · 2 active endpoints, archive available (the rotation's own probe, 2026-10-18 16:47 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 abstract

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

Protocol contracts the producer knows on abstract: Relay.link DepositSource 0x4cd00e387622c35bddb9b4c962c136462338bc31.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain

chain: abstract (2741)
transaction: 0x2a6788332ccb61ab0037549c9f0ee66d6e4485d8eb64ef04cf61a3a37398cbe9
block: 87835343
time: 2026-10-18 16:44 UTC
protocol: layerzero_v2

2 · typed transition

order key: layerzero_v2:0xe85d07f6a9f221d7b39acd7a95526fe4088dacdb851e6abc807d00f1dbe87e84
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: 0xe55a0d61b30ee2a7fe2e96a89116e0533c312e38529020cc58a685255c0b65f8
pipe seq: 313540
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-18 16:48 UTC

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

[ 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 abstract 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:2741

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