The vault for the quantum chain
Real self-custody for QTC. Keys are forged in your browser with post-quantum ML-DSA signatures, addresses derive from the chain's own Poseidon2 hash, and the vault is encrypted before it ever touches disk. No accounts, no servers, no seed ever leaves this page.
✨ Create a new wallet
Forge a fresh 24-word recovery phrase and an ML-DSA keypair. Takes about a minute — write the words down.
📥 Import a wallet
Bring a wallet you already made here — or anywhere that uses the documented derivation.
💾 Restore a vault file
Load an encrypted vault backup you exported earlier. You'll still need its password.
📝 Write these 24 words down — now
This is the only time they are shown. Anyone with these words owns the wallet. Store them on paper or steel, never in a screenshot or cloud note.
🔐 Encrypt the vault
Pick a strong password. It encrypts the vault on this device (PBKDF2-HMAC-SHA256, 250,000 rounds + AES-GCM-256). It cannot recover your wallet — only the 24 words can.
🔓 Unlock the vault
Vault found on this device. Enter your password — decryption happens locally.
Forgot the password? Re-import with your 24 words — but first remove the locked vault with “Forget this device”.
Your address
Balance
- Transferable
- —
- Reserved
- —
- Frozen
- —
- Tx count (nonce)
- —
- Source
- —
Read straight from chain storage (System.Account) over the RPC node below — never estimated.
🔌 Node connection
- Chain
- —
- Block
- —
- Runtime
- —
📤 Send QTC
Builds a real Balances.transfer_keep_alive extrinsic, signs it with your
ML-DSA key under the chain's QUANTUS_EXTRINSIC context, and broadcasts it to the connected node.
Review the transfer
- To
- —
- Amount
- —
- Network fee (est.)
- —
- Total debit
- —
- Nonce
- —
- Era
- —
🔍 Extrinsic inspector — see exactly what gets signed
⚠️ Broadcasting is final: once included, only the recipient can send it back. Double-check the address — the first and last 6 characters are shown above.
🧾 Recent transfers
Pulled from the public Subsquid indexer. If it's unreachable, the wallet says so — it never invents history.
Not loaded yet.
🗝️ Recovery phrase
Reveals the 24 words. Never type them anywhere except a wallet you trust.
📋 Key details
- Public key
- —
- Account id
- —
- Derivation
- BIP-39 24 words → PBKDF2-HMAC-SHA512(2048) → first 32 bytes → ML-DSA keygen (deterministic). Quantus-specific path, documented openly.
- Signing context
- QUANTUS_EXTRINSIC (FIPS-204 domain separation, per upstream signing_context.rs)
💾 Backup & danger zone
Wiping deletes the encrypted vault from this browser only. Your 24 words still recover the wallet anywhere.
📜 How the crypto was verified
- Address =
Poseidon2(public_key)(Goldilocks field) → SS58 prefix189— fromqp-dilithium-crypto 0.6.1 traits.rs+quantus-cli address_format.rs. - Signature =
DilithiumSignatureScheme::Dilithium65([sig 3309 B ‖ pubkey 1952 B])—primitives/dilithium-crypto/src/types.rs. - Signatures are FIPS-204 with context
QUANTUS_EXTRINSIC—signing_context.rs; plain-context signatures are rejected on-chain. - Extrinsic =
Balances(pallet 2) ·transfer_keep_alive(call 3) — runtimeconstruct_runtime!+pallet-balances 46.0.0. - Extension pipeline order (12 extensions) read from
runtime/src/lib.rsTxExtension; payload layout matchessp-runtime 45.0.0 SignedPayload.
Upstream: Quantus-Network/chain · verified Sept 30, 2026.