BMIC vs Tezos (XTZ) — Is Tezos Quantum Safe?

Tezos and Quantum Computing: The Core Problem

Tezos (XTZ) launched on mainnet in September 2018, positioning itself as a self-amending blockchain with on-chain governance and formal verification of smart contracts. Its multi-curve key flexibility — supporting secp256k1, Ed25519, and NIST P-256 (p256) — was designed for developer choice. But from a post-quantum security perspective, offering three flavours of elliptic curve cryptography is not the same as offering quantum resistance.

All three curves — secp256k1, Ed25519, and p256 — rely on the elliptic curve discrete logarithm problem (ECDLP) as their mathematical hardness assumption. Shor's algorithm, running on a cryptographically relevant quantum computer (CRQC), solves ECDLP in polynomial time for any elliptic curve group. Curve choice is irrelevant to quantum immunity.

Tezos Baker and Wallet Key Architecture

Registered On-Chain Keys

Tezos uses two distinct key pairs for bakers: a consensus key (used to sign Tenderbake attestations and block proposals) and a manager/payment key (used to receive rewards and initiate tz-address operations). Both must be revealed on-chain — once a manager key's public key is revealed via a Reveal operation, it is permanently archived in Tezos ledger history.

Three Supported Curves — All Vulnerable

• tz1 addresses (Ed25519): Curve25519 Edwards form. Still ECDLP-based. Shor's algorithm applies.
• tz2 addresses (secp256k1): Bitcoin-style ECDSA. ECDLP-based. Shor's algorithm applies.
• tz3 addresses (p256 / NIST P-256): NIST-standardised ECDSA. ECDLP-based. Shor's algorithm applies.

Tenderbake Consensus (2022 Upgrade)

The 2022 Tenderbake upgrade replaced Emmy* with a BFT-style protocol requiring ⅔+1 weighted attesting power per block. Every attestation is a signed on-chain message tied to the baker's registered consensus key. These attestations are permanently archived in Tezos block headers — a continuously growing HNDL corpus extending back to September 2018.

On-Chain Governance Votes

Tezos governance proceeds through four on-chain phases: Proposal, Exploration Vote, Cooldown, Promotion Vote, and Adoption. Every baker vote is a cryptographically signed on-chain transaction. A CRQC attacker who derives baker private keys can cast fraudulent governance votes — including votes to adopt a malicious protocol amendment that further embeds the attacker's access.

CRQC Attack Path: Tezos Baker Takeover

The following four-step attack path illustrates how a CRQC breaks Tezos baker security once sufficient quantum hardware is available:

1. Harvest (now, pre-CRQC) Archive all baker consensus public keys and manager key reveal transactions from Tezos block history via RPC snapshot. Every baker who has ever participated in consensus has an exposed public key. 8-year corpus from September 2018.
2. Derive (CRQC, future) Run Shor's algorithm against target baker public keys — Ed25519, secp256k1, or p256 — to derive the corresponding private keys. Each derivation takes seconds to minutes on a sufficient CRQC; all three curves are equally solvable.
3. Forge (CRQC, future) Use derived consensus private keys to sign forged Tenderbake attestations for any block. Forge a ⅔+1 majority using top-delegate keys (the largest bakers, whose public keys are most prominently recorded). Redirect block finality, double-bake to slash legitimate bakers, or inject invalid block headers.
4. Exploit (CRQC, future) Use derived manager key private keys to drain staking rewards, governance voting balances, and XTZ holdings from compromised baker accounts. Forge governance votes to adopt malicious protocol upgrades — Tezos's self-amending mechanism becomes a self-amending attack vector. Drain any DeFi protocol admin keys (Plenty Network, Youves, Quipuswap) controlled by the same keys.

8-Year Harvest-Now-Decrypt-Later Corpus

Tezos mainnet launched in September 2018. Every baker Reveal operation, attestation, and governance vote since then is part of the permanent HNDL corpus — 8 years of exposed key material as of August 2026.

Etherlink and Smart Rollup Operator Keys

Tezos introduced Smart Rollups (2023) and Etherlink — a WASM-powered EVM-compatible L2 on Tezos — in 2024. Etherlink allows EVM-compatible accounts using standard secp256k1 ECDSA keys, adding a new quantum-vulnerable surface on top of the base layer.

Three Quantum-Vulnerable Layers on Etherlink

• Etherlink EVM wallets — standard secp256k1 accounts; same quantum exposure as Ethereum.
• Smart Rollup kernel operator keys — the entity managing the rollup kernel uses a Tezos L1 key (Ed25519/secp256k1/p256) to commit rollup state to L1.
• Refutation game participants — dispute resolution on rollup validity is signed at L1 using the same quantum-vulnerable key types.

A CRQC attacker who derives a Smart Rollup kernel operator key can commit fraudulent rollup states, enabling EVM-side asset theft while appearing valid at the Tezos L1 layer — a cross-layer amplification analogous to optimistic rollup fraud on Ethereum.

Tezos DeFi Ecosystem: Admin Key Exposure

The Tezos DeFi ecosystem includes several protocols whose admin and upgrade keys use the same quantum-vulnerable key types:

• Plenty Network / Spicy Swap — AMM admin keys for liquidity pool parameter updates.
• Youves — algorithmic stablecoin governance admin keys.
• Quipuswap — DEX fee recipient and governance keys.
• Flame / Harbinger oracles — price oracle signing keys (price-feed manipulation vector).
• Tezos Domains — domain record admin keys (DNS-like redirect attack vector).

Because Tezos contracts are formally verified via Michelson for correctness, not for key security, formal verification provides no barrier against CRQC-derived key compromise of admin roles.

Technical Comparison: BMIC vs Tezos (XTZ)

How BMIC Approaches Quantum Security

BMIC is a presale crypto project built with three NIST FIPS post-quantum standards finalised in August 2024 as core cryptographic infrastructure:

• NIST FIPS 203 (ML-KEM / CRYSTALS-Kyber) — lattice-based key encapsulation mechanism. Replaces ECDH key exchange. No known quantum polynomial speedup.
• NIST FIPS 204 (ML-DSA / CRYSTALS-Dilithium) — lattice-based digital signatures. Replaces secp256k1/Ed25519/p256 for transaction signing.
• NIST FIPS 205 (SLH-DSA / SPHINCS+) — stateless hash-based signature scheme. Provides a mathematically independent backup to lattice-based schemes; relies only on hash function security, not algebraic structure.

The three-standard approach means BMIC's security does not rest on a single hardness assumption. Even a hypothetical breakthrough against lattice problems would leave hash-based SLH-DSA intact — unlike Tezos's multi-curve approach, which shares the same ECDLP assumption across all three curves.

BMIC also implements ERC-4337 account abstraction, which architecturally decouples wallet signing from the classical private-key model, reducing the attack surface available to a future CRQC versus a conventional EOA or baker-key model.

NSM-10 and Institutional Compliance

US National Security Memorandum 10 (NSM-10) requires federal agencies and critical infrastructure operators to inventory quantum-vulnerable cryptography and migrate to NIST-approved PQC algorithms by 2030. Institutional investors — pension funds, sovereign wealth funds, regulated custodians — operating under NSM-10 or equivalent frameworks face increasing pressure to evaluate the quantum posture of digital asset holdings.

Tezos has no published NIST PQC migration roadmap as of August 2026. Institutions holding XTZ or operating Tezos baker infrastructure have no clear path to NSM-10 compliance on the protocol layer. This is a distinct risk dimension beyond retail investor quantum concerns.

BMIC implements NIST FIPS 203/204/205 from genesis — not as a future migration target — positioning it as the only presale-stage crypto project with built-in NSM-10 alignment at the cryptographic layer.

Related Quantum Comparisons