Appearance
PQC: how far it goes
An EmpoorioChain account can be protected with post-quantum signatures. The chain cannot. Both sentences are true. Say both.
What is done and checkable
| Piece | Where | What it does |
|---|---|---|
| ML-DSA (FIPS 204) inside WASM | pallet-pqc-keys | Real verification in the runtime, compiles to wasm32-unknown-unknown |
| Per-account PQC level | AccountPqcLevels | Each account chooses |
| Sealed accounts | CuentasSelladas | Reject the classical signature |
| On the transaction path | CheckPqcPolicy, first in SignedExtra | Checked before anything else |
Registering a PQC key does not protect by itself. The day classical signatures break, the attacker signs classically and ignores the registered key. The account had armour and an open door. Sealing closes the door.
Ordinary transfers do not require a PQC signature. Accounts with no policy pass CheckPqcPolicy with None/None (0x00 0x00). See Extrinsics.
CheckPqcPolicy is first so the PQC signature covers genesis, spec, tx version, era, nonce and tip — not only the call. Last in the tuple would make a captured transfer(bob, 100) replayable forever.
What is not protected
Consensus is classical.
- Aura signs with sr25519.
- GRANDPA signs with ed25519.
- Authority keys are in chain state, public.
A quantum attacker who can break elliptic curves can forge blocks and finality justifications even if every account were post-quantum. Protecting accounts and leaving consensus classical is a good lock on a glass door.
There is no production Aura/GRANDPA with PQC in Polkadot-SDK. No Substrate chain in production has post-quantum consensus. Projects that say “we are post-quantum” are, at best, talking about accounts.
What you may say
True:
EmpoorioChain lets a DRACMA account protect itself with optional ML-DSA signatures, for accounts that seal explicitly. Verification is in the runtime.
False:
- “EmpoorioChain is post-quantum.”
- “DRACMA is protected against quantum computers.” Only sealed accounts, and only against direct theft, not against forged blocks.
- “We are the first post-quantum chain.”
Levels
| Level | Meaning | Status |
|---|---|---|
| 1 | Register a PQC key | done |
| 2 | Seal an account and reject classical signatures | done |
| 3 | Root / runtime upgrades signed with PQC | not done |
| 4 | Aura/GRANDPA post-quantum | does not exist in Polkadot-SDK |
A public “we are PQC” claim only starts to make sense at level 3, and still with the caveat that it is optional and per-account. Level 3 is the cost-effective one: it protects the ability to react (ship a runtime that changes crypto). If the key that authorises set_code is classical, the attacker ships their runtime.
AccountId is the public key
Substrate AccountId is the public key, 32 bytes, visible from account creation. Bitcoin P2PKH hashes the key until first spend. Here there is no such hide. Unsealed accounts are stealable on the day classical signatures break, whether they have transacted or not.
