Seed Round: $0.25/FRAC — Listing at $1.00 (300% ROI) — Buy Now
← Blog
#post-quantum#cryptography#ethereum

Post-quantum signatures for Ethereum developers: a practical intro

Why ECDSA is on borrowed time, what NIST FIPS 204 (Dilithium) means for your app, and how to add post-quantum signing in minutes.

Every Ethereum account is secured by ECDSA. A cryptographically-relevant quantum computer breaks ECDSA — and NIST already set the clock: deprecated after 2030, prohibited after 2035. Anything you secure today with classical signatures has a quantum expiry date.

NIST standardized the replacements in 2024: ML-DSA (CRYSTALS-Dilithium, FIPS 204) for signatures and ML-KEM (Kyber, FIPS 203) for key exchange. These are lattice-based and resistant to all known classical and quantum attacks — not "unbreakable" (no scheme is forever), but the standard the world is migrating to.

The catch for builders: PQC signatures and keys are larger (Dilithium-2: ~1.3 KB public key, ~2.4 KB signature), so EVM verification on-chain is expensive — there are no native precompiles. That is exactly why a from-scratch post-quantum L1 (which verifies these in consensus) plus a simple signing API is useful: you get NIST-standard PQC without re-implementing the math.

In practice you do three calls: generate a keypair, sign a message, verify. Payment settles in USDC on Base — no card, no signup wall, free tier to experiment. Honest scope: it is for developers exploring PQC, not yet third-party audited bank infrastructure.

Try it yourself — live, free, verifiable in 30 seconds:

Try the PQC API ($29/mo, USDC)
FRACTAL AI S.A.S. · Honest claim: resistant to all known classical & quantum attacks per NIST FIPS 203/204 — not “unbreakable”.