Appearance
Changelog
User-visible changes to the platform — new chains, new transports, limit and error-shape changes. Newest first.
Changes that affect what your code sees (error shapes, limits, endpoints) are marked Breaking or Behaviour. Internal work — node operations, capacity, performance — isn't listed unless you'd notice it from the outside.
2026-07
Dogecoin is available — /doge
https://rpc.au.ro/doge now serves dogecoind JSON-RPC, same shape as the rest of the Bitcoin family. See Dogecoin.
Cosmos Hub — corrected documentation Behaviour
No change to the service; the docs were wrong and are now correct. If you built against the old page, read Cosmos Hub again:
https://…/cosmosis the LCD REST API, not CometBFT JSON-RPC. A JSON-RPC POST there is answered{"code":12,"message":"Not Implemented"}; CometBFT paths like/cosmos/statusreturn501.- The CometBFT RPC (
status,abci_query,subscribe, …) is served over WebSocket —wss://…/ws/cosmos. /cosmosdoes not batch (it's REST — an array POST returns-32603).- CosmJS's
Tendermint37Clientcannot reach either transport; use the LCD, or gRPC for typed module queries.
Error catalog additions Behaviour
No new failure modes — these always existed and are now documented (Errors):
-32603 unexpected backend response format— a batch sent to a chain that isn't JSON-RPC.-32603 no response for request id in batch.-32700 failed to read request— distinct frominvalid JSON-RPC request.- A chain path with no route returns a gateway
404 {"message":"no Route matched with those values"}— not-32601.-32601means the chain is known but not served at your location.
WebSocket streaming — wss://…/ws/<chain>
Native subscriptions on eth, bsc, polygon, avax, solana, xrp, cosmos and cardano — you speak each chain's own subscription protocol; the stream itself is free (only the handshake is gated). See WebSockets.
gRPC — two entry ports
Native gRPC for Cosmos Hub and TRON. rpc.au.ro:8443 serves every call shape including server reflection; rpc.au.ro:443 handles unary + server-streaming with explicit descriptors. A ready-made cosmos.protoset is published. See gRPC.
Faster key revocation Behaviour
A revoked key now stops working within seconds at the proxy itself, even if the gateway's own credential lags — it answers 401 / -32012 API key revoked, and a revoked key inside a batch kills the whole batch before anything runs. See Security.
Honest per-location chain errors Behaviour
A chain the platform supports but that isn't served where you're connected now answers -32601 chain not available at this location: <chain> instead of a misleading backend error. Your key is fine — see Endpoints.
New reference pages
Platform limits, Support & SLA, Billing and a full per-chain Compute Units matrix.
Something changed and you're not sure why?
Every response carries an X-Correlation-ID. Quote it in a support ticket and we can trace the exact request.