A Quantum Chain account is a post-quantum keypair with a 20-byte address derived from the public key.
The address format is identical to Ethereum on the wire, so existing block explorers, ABIs, and address-checksum logic work unchanged.
All three are produced by make all.
Create a new account
Output:
The mnemonic is displayed once and never written to disk. Store it offline. Anyone with the mnemonic can regenerate the private key.
keystore/ folder under your --datadir:
Recover from a mnemonic
The recovered keypair is deterministic — the same mnemonic always produces the same address.
Inspect a keystore
Sign messages offline
Returns the post-quantum signature in hex.
The ciphertext holds the encrypted post-quantum private key. The schema matches the standard Ethereum Web3 secret-storage definition, so any tool that can decrypt a Web3 keystore can decrypt a Quantum Chain keystore — the difference is only what the plaintext represents.
Use a keystore with geth
--unlock and --allow-insecure-unlock are intended for development only. In production use Clef or an external signing service.Use Clef for hot signing
Clef ships with this repository and is updated to handle post-quantum signing.
Clef listens on a Unix socket and prompts you (or your custom rule script) for each signing request. Connect geth to clef with --signer /path/to/clef.ipc.
For multi-user, audited, policy-driven signing, use Qustody. Qustody never holds private keys; it orchestrates signing through an external post-quantum signer that you control.
Where to go next
