WebSockets roadmap

There is no public WebSocket endpoint yet. This page exists so you don't spend an afternoon discovering that — and shows how to cover the common subscription use cases today.

What's coming

A wss://rpc.lab.au.ro/ws/<chain> gateway (the internal service already exists) with API-key auth via header or Sec-WebSocket-Protocol, streaming the same event feed webhooks deliver: new blocks, address activity, health. EVM eth_subscribe passthrough is under evaluation after that.

Covering subscriptions without WS

New blocks (any chain)

Server-side caching makes polling cheap — eth_blockNumber costs 1 CU and is cached 2 s, so a 3–4 s poll is fresh and inexpensive:

let last = 0n
setInterval(async () => {
  const n = await client.getBlockNumber()      // viem/ethers, see chain pages
  if (n > last) { last = n; onNewBlock(n) }
}, 4000)

bitcoind chains: poll getblockcount (10 s cache) or getbestblockhash.

Push instead of pull

Webhooks deliver new_block / address_activity events to your HTTPS endpoint with signed payloads and retries — for most "react to chain activity" workloads they replace a WS subscription outright, and they survive your process restarts.

Pending transactions

Mempool streaming is WS-territory; until then there is no newPendingTransactions equivalent. If your product depends on it, tell us — it shapes the WS rollout priority.