Talk to the chain directly.
The Chain Console is a live JSON-RPC workbench for Quantus: connect to any node's WebSocket RPC, run one-click recipes against real chain state, fire custom methods, and watch live subscriptions. No mocks, no snapshots — if the endpoint is unreachable, it says so.
Connection
Node identity
Recipes
One click, one method, a human-readable summary plus the raw JSON. Every value comes from the node you connected to.
History
Every call this browser made, newest first. Re-run any of them.
Custom method
Any method the node exposes — including ones with no recipe. Params are a JSON array. Ctrl+Enter sends.
Live subscriptions
Open a subscription and the node pushes updates over the same socket. Start one, watch the feed, stop it when done — subscriptions die with disconnect.
Feed
Method reference
The methods a Substrate node exposes, with Quantus notes where this builder has learned something the hard way. Public RPCs commonly disable author_* and txWatch_* — a "method not found" there is node policy.
How this console works
The wire protocol
Quantus nodes speak JSON-RPC 2.0 over WebSocket — the same protocol every Substrate/Polkadot-SDK chain uses. Each request is {"jsonrpc":"2.0","id":1,"method":"system_chain","params":[]}; the node answers with {"jsonrpc":"2.0","id":1,"result":"Quantus"}. The id lets many calls share one socket — this console fires the node-identity recipe's five calls in parallel.
Subscriptions
A *_subscribe* call returns a subscription id, then the node pushes notifications on the same socket. That is how the live head feed works — no polling. Unsubscribe (or disconnect) when you are done; a forgotten subscription is a leak on the node.
Read first, write carefully
Everything here is read-only except author_submitExtrinsic, which is gated behind a review screen and an explicit checkbox. The console never asks for keys — it only moves bytes you already signed elsewhere (the Airgap Desk produces them).
Etiquette
wss://rpc.quantus.network is a shared public endpoint. Do not poll it in a tight loop from scripts — subscribe instead, cache aggressively, and run your own node for heavy work (the Node Operator Desk shows how).
Key facts this console relies on
- SS58 address prefix 189, 12 decimals, 1 QTC = 1012 planck (chain/node/src/chain_spec.rs, runtime)
- Account storage: System.Account map, Blake2_128Concat over the 32-byte account id — the same key derivation your wallet uses
- Existential deposit 0.001 QTC — accounts below it can be reaped
- txWatch_* methods are Quantus-specific pool-listener additions — the Mempool Desk is their full desk
Further reading
- docs.quantus.com — official docs
- quantus-api-client — the official Substrate WS API client
- Quantus-Network org — chain source this console's crypto was verified against