steinchain
Devnet live

The layer-1 that is post-quantum from genesis.

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.

Why post-quantum, and why now

Most blockchains are secured by elliptic-curve signatures. A large enough quantum computer breaks those, and a public ledger cannot take its history back.

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.

The ledger is permanent

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.

Migration is the hard part

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.

How Stein is built

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.

Signatures

Two post-quantum families

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.

Verification

Every node checks everything

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.

Size

790-byte transfers

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.

Agility

Ready for the next standard

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.

Hashing

BLAKE3, separated by purpose

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.

Transport

Post-quantum between nodes

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.

The numbers

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.

SchemeStandardSignatureTransferFirst transfer, with key
FN-DSA-512 defaultdraft FIPS 206666 B790 B1,688 B
ML-DSA-44FIPS 2042,420 B2,544 B3,857 B
ML-DSA-65FIPS 2043,309 B3,433 B5,386 B
69%

smaller transfers with FN-DSA-512 than with ML-DSA-44.

~66,000

FN-DSA signature verifications per second on one core, measured on a development machine.

1 s

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.

Where it stands

Stein is in development. This is what exists today and what comes next.

Built
  • Devnet with post-quantum transactions, accounts and fees
  • FN-DSA-512 and ML-DSA accounts on one chain
  • Follower nodes that re-verify every block, over post-quantum TLS
  • steinscan, the live block explorer
  • steinwallet, a browser wallet that signs in WebAssembly
  • A command-line wallet and node, in Rust
Next
  • Hardening: fuzzing, state on disk, RPC rate limits
  • Peer-to-peer networking and transaction gossip
  • Proof-of-stake consensus with deterministic finality, formally modelled
  • Public testnet, faucet and wallet SDK
  • Smart contracts in WebAssembly
  • Independent audits, then mainnet

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.

Try it