EOS launched in June 2018 with Delegated Proof of Stake and secp256k1 ECDSA. All 21 active Block Producer signing keys are published on-chain in every block — 8+ years of archived K1/R1 signatures covering every governance actor. BMIC ships NIST FIPS 203/204/205 from day one.
Get BMIC — Quantum-Safe from Day One →| Criterion | BMIC | EOS |
|---|---|---|
| Signature scheme | ML-DSA (FIPS 204 / Dilithium) | secp256k1 ECDSA (K1) primary; secp256r1 (R1) secondary |
| NIST FIPS PQC standard | FIPS 203 + 204 + 205 ✅ | None deployed ❌ |
| Quantum threat | None (lattice-based, no ECDLP) | Critical — both secp256k1 and secp256r1 broken by Shor's |
| HNDL archive since | N/A (PQC) | June 2018 — 8+ years |
| Block Producer (BP) key exposure | Not applicable | 21 active BPs; all producer keys public on-chain — harvestable since 2018 |
| Account key model | ML-KEM/DSA protected | Owner + Active key hierarchy — all keys archived in account actions |
| Governance attack via CRQC | Not applicable | 21 BP keys → quorum forgery → RAM/CPU parameter manipulation |
| PQC roadmap | Deployed at launch | No published NIST-aligned PQC migration plan as of Oct 2026 |
EOS supports two elliptic-curve signature suites: K1 (secp256k1, default for most accounts) and R1 (secp256r1 / P-256, used in Antelope-based chains for WebAuthn compatibility). Both curves rely on ECDLP for security. Shor's algorithm solves ECDLP for all elliptic-curve groups — the specific curve is irrelevant. An EOS account secured with either K1 or R1 keys is equally vulnerable to a CRQC adversary.
EOS uses Delegated Proof of Stake (DPoS) with 21 active Block Producers. All 21 producer signing keys are published on-chain in every block they produce — they have been since EOS mainnet launched in June 2018. A CRQC adversary needs to recover only a simple majority (11 of 21) of BP private keys to forge the multisig threshold needed for on-chain governance actions, including RAM price manipulation, CPU parameter changes, and smart contract blacklisting. All 21 key archives are publicly available and globally replicated.
EOS accounts use a permission hierarchy with Owner and Active keys (and custom permission levels). Every account action signs with the Active key, broadcasting the secp256k1/R1 signature on-chain. Owner key usage (account recovery) also produces on-chain signatures. Both are permanently archived. An account that has ever performed any action — transfer, vote, contract interaction — has exposed its Active key signature to the HNDL archive.
EOS mainnet launched in June 2018 — over 8 years of continuous operation. Given EOS's high throughput (capable of thousands of TPS historically), the volume of archived K1/R1 signatures is among the highest of any smart-contract chain. Every EOS account action, every BP block, every MSIG threshold signature has been permanently archived since launch.
EOS migrated to the Antelope framework (formerly EOSIO) along with sister chains Telos, WAX, and UX Network. All Antelope-based chains share the same secp256k1/secp256r1 cryptographic stack — the framework change did not introduce post-quantum primitives. The quantum exposure is consistent across all Antelope forks.
Module Lattice Key Encapsulation. No elliptic-curve structure. No known quantum attack.
Module Lattice Digital Signature. Replaces secp256k1/R1 for all BMIC signing. MLWE-based security.
Stateless Hash-Based Signature. No algebraic structure exploitable by quantum algorithms. Backup layer.
No. EOS uses secp256k1 ECDSA (K1) and secp256r1 (R1) — both elliptic-curve schemes broken by Shor's algorithm. Its 8+ year HNDL archive and 21 publicly exposed BP key archives make it a significant quantum target. No NIST-aligned post-quantum primitive has been deployed to EOS as of October 2026.
No. secp256r1 (P-256) provides better classical parameter provenance than secp256k1, but both rely on ECDLP — which Shor's algorithm breaks regardless of curve. R1 key support adds WebAuthn/passkey compatibility for classical security; it provides zero quantum protection.
BMIC deploys NIST FIPS 203/204/205 — no ECDLP dependency, no known quantum attack — from day one. EOS deploys secp256k1/R1 with 8+ years of archived signatures including all 21 BP keys. Visit bmic.ai for presale details. DYOR.