[ RPC · chain 1135 ]

lisk, with proofs.

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

HTTPS: https://coord.taifoon.dev/gw/rpc/1135
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 42 ms average, 52 ms p95, 88.1 % 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 lisk

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

Protocol contracts the producer knows on lisk: Across Protocol V3 DepositSource 0x9552a0a6624A23B848060AE5901659CDDa1f83f8 · Across Protocol V3 FillTarget 0x9552a0a6624A23B848060AE5901659CDDa1f83f8 · Relay.link DepositSource 0x4cd00e387622c35bddb9b4c962c136462338bc31 · Li.Fi / Jumper DepositSource 0x1231DEB6f5749EF6cE6943a275A1D3E7486F4EaE · Meson Finance DepositSource 0x25ab3efd52e6470681ce037cd546dc60726948d3.

[ Per-contract events ]

An event, as the lambda sees it

1 · raw event on chain

chain: lisk (1135)
transaction: 0x059184d118d27c82889ca0b9d96ccae1255f75cfbdd90eea65ad98f4b22df979
block: 38806538
time: 2026-10-18 16:44 UTC
protocol: layerzero_v2

2 · typed transition

order key: layerzero_v2:0x3a469907aef191a50904a47802104f7513fba1c5e8cf55706a2a528b244ee435
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: 0x30340a66c42c1a9c4f23f24ef9d2e3d539309fc0b680a292a016cc7a4e509cf9
pipe seq: 313546
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/0x3a469907aef191a50904a47802104f7513fba1c5e8cf55706a2a528b244ee435

[ 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 lisk 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:1135

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