The signatures break
Shor's algorithm recovers a private key from an elliptic-curve public key. That covers ECDSA, EdDSA and BLS: the schemes behind nearly every chain in use today.
Every signature on Stein Chain is ML-DSA (FIPS 204) or FN-DSA (draft FIPS 206), and every block is re-verified by every node. No ECDSA, no EdDSA, no BLS: nothing a quantum computer breaks.
Most blockchains are secured by elliptic-curve signatures. A large enough quantum computer breaks those, and a public ledger cannot take its history back.
Shor's algorithm recovers a private key from an elliptic-curve public key. That covers ECDSA, EdDSA and BLS: the schemes behind nearly every chain in use today.
Public keys published on a chain stay there. An account that has ever spent has its key on record, waiting for the day the mathematics stops protecting it.
Moving a live chain to new signatures means every holder acting before the deadline. Stein starts where that migration ends: there is no classical scheme to retire.
Post-quantum signatures are far larger than the ones they replace. The design is about keeping transactions small and trusting nothing that has not been checked.
FN-DSA-512 (draft FIPS 206) is the default for accounts: 666-byte signatures. ML-DSA (FIPS 204) is accepted for accounts and required for validators.
A node verifies every signature in a block, and the resulting state, before it accepts the block. Nothing a block producer claims is taken on trust.
An account's public key goes on chain once, with its first transaction. Every later transfer carries a signature only, and fees are charged per byte.
Every key and signature carries a scheme tag. A new standard is added as a new tag, with no change of format, and accounts on different schemes transact freely.
Every hash and every signed message has its own domain, so a value made for one purpose can never be replayed as another. Transaction ids cover the body, not the signature.
Nodes talk over TLS 1.3 with a hybrid ML-KEM key exchange, so traffic recorded today cannot be decrypted by a quantum computer later.
What a transfer costs in bytes, by signature scheme. Bytes are the scarce resource on a post-quantum chain, so they are what the fee is charged on.
| Scheme | Standard | Signature | Transfer | First transfer, with key |
|---|---|---|---|---|
| FN-DSA-512 default | draft FIPS 206 | 666 B | 790 B | 1,688 B |
| ML-DSA-44 | FIPS 204 | 2,420 B | 2,544 B | 3,857 B |
| ML-DSA-65 | FIPS 204 | 3,309 B | 3,433 B | 5,386 B |
smaller transfers with FN-DSA-512 than with ML-DSA-44.
FN-DSA signature verifications per second on one core, measured on a development machine.
target block time. The devnet produces a block when transactions are waiting.
Measured figures are from the protocol specification, section 2, and exclude networking and consensus. They are the ceiling of one node's processor, not network throughput.
Stein is in development. This is what exists today and what comes next.
Today the devnet has a single validator, and its STEIN has no value. It can be reset at any time. Nothing here is an offer of a token or an investment.
Make an account in your browser and send a post-quantum transfer on the devnet.
Blocks, transactions, accounts and validators, live, with every signature scheme shown.
The node, the wallet, the protocol specification and how to run a follower of your own.