The developer console for the quantum-era chain
Every constant on this page was read out of the upstream chain source — chain_spec.rs and the runtime — not copied from memory. Build against it: pallet indices, fees, units, accounts, and working connection recipes.
Chain constants
Read from node/src/chain_spec.rs and runtime/src/lib.rs on 2026-09-30.
Runtime pallet map
The full index map from #[frame_support::runtime] in runtime/src/lib.rs — including the vacant indices where pallets were removed (kept empty so downstream indices stay stable). Type an index number to jump straight to it.
| Index | Pallet | Status |
|---|
Unit converter — exact to the planck
QTC uses 12 decimals: 1 QTC = 1012 plancks (runtime UNIT). Math runs on BigInt — no floating-point dust. The existential deposit is 0.001 QTC (1,000,000,000 plancks).
Accounts & keys
The part of Quantus that breaks Substrate muscle memory: accounts are keyed by post-quantum ML-DSA, not sr25519.
Address format
- SS58 prefix 189 — every Quantus address starts with
qz…(qznY8nwuvWcCCVys4da1oQdysyh8YUZYRjRqgk3S8Wos8kbau) - 32-byte public key + 2-byte blake2b checksum, base58-encoded (standard SS58)
- Human-readable checkphrases come from qp-human-checkphrase — the same encoding SafeSend verifies
Key type
- ML-DSA (Dilithium family) keys — ML-DSA-65 / ML-DSA-87 since the genesis block
- Signatures are ~2.6–4.6 KB; that's why Quantus transactions are ~7 KB and need native aggregation
- Do not generate keys with polkadot-js's sr25519/ed25519 keyring — create them in the official wallet or
quantus-cli
Balance rules
- Existential deposit: 0.001 QTC — accounts below it are reaped
- Use
balances.transferKeepAliveso you can't accidentally kill your own account - Reversible transfers (SafeSend) hold funds on a delay — the pallet can
recover_fundsto the sender if the receiver never claims
Connection recipes
Copy-paste starting points. Honest limits are printed with each recipe — the indexer at sqm.quantus.com only accepts browser calls from allowlisted official domains, so browser apps should read the same-origin snapshot; GraphQL works from servers. No public RPC endpoint is published in the docs as of Sept 2026 — run your own node from the chain repo for RPC.
JSON-RPC request builder
Point this at your own node (http://localhost:9944 by default). Pick a method, fill the params, copy the JSON — paste into curl or your HTTP client.
Upstream repo map
Key repos under Quantus-Network — what each one is for. Activity checked 2026-09-30.
Run a node
Everything you need is in the chain repo — the README covers binary and Docker builds, and MINING.md covers mining setup. No command below is invented; click through to the source.
- Read Quantus-Network/chain — README (build), MINING.md (mining), Dockerfile (container build)
- Generate and manage accounts with quantus-cli — keys are ML-DSA, keep the seed phrase offline
- Point integrations at your node's HTTP-RPC (
localhost:9944) and WS (localhost:9945) — or use the quantus-api-client WebSocket library - Mining: grab quantus-miner; benchmark with qpow-benchmark. Our Mining Studio walks the whole setup.