What Is Monad?
Monad is an EVM-compatible Layer 1 blockchain engineered for extreme throughput. Its core innovation is pipelined parallel EVM execution: transactions within a block are analysed for data dependencies and executed in parallel across multiple CPU cores, with sequential fallback only for dependent transactions. Combined with MonadBFT (a pipelined HotStuff-based BFT consensus protocol), MonadDb (a custom optimised storage layer replacing LevelDB/RocksDB), and asynchronous I/O separating execution from disk access, Monad targets 10,000 TPS with 1-second block times.
Monad raised $225 million in April 2024 from Paradigm (lead), Electric Capital, Greenoaks, Coinbase Ventures, and others at a $3 billion valuation — one of the largest crypto fundraises in 2024. The testnet launched in February 2025 and attracted over 3.5 million wallets in its first month, making it one of the fastest-ramping EVM testnets on record. Mainnet launched in 2025. The MON token is the native gas and governance token.
From a developer perspective, Monad is a direct drop-in for Ethereum: all Solidity and Vyper contracts deploy unchanged, all EVM tooling (Hardhat, Foundry, Ethers.js, Viem) works without modification, and all wallet infrastructure (MetaMask, WalletConnect, ERC-4337 bundlers) operates identically. This frictionless EVM compatibility is Monad's primary developer value proposition — and its primary quantum security liability.
Consensus: MonadBFT (pipelined HotStuff BFT) · Execution: Parallel EVM with optimistic concurrency control · Storage: MonadDb (custom Patricia trie) · Block time: 1 second · Target TPS: 10,000 · Key scheme: secp256k1 ECDSA (EVM-identical) · Account model: EVM EOA + ERC-4337 smart accounts
BMIC vs Monad (MON) — Side-by-Side
| Category | BMIC | Monad (MON) |
|---|---|---|
| Primary key scheme | ML-KEM (FIPS 203) + ML-DSA (FIPS 204) + SLH-DSA (FIPS 205) QUANTUM SAFE | secp256k1 ECDSA (EVM-standard) VULNERABLE |
| NIST PQC standards | FIPS 203, 204, 205 — all three implemented ✅ | None. No NIST FIPS PQC standard for EVM EOA secp256k1 (Oct 2026) ❌ |
| Shor's algorithm vulnerability | Not applicable — ML-KEM/ML-DSA/SLH-DSA have no known quantum polynomial attack ✅ | secp256k1 ECDLP solvable by Shor's algorithm on a CRQC — ~512-qubit fault-tolerant register ❌ |
| HNDL archive speed | N/A (post-quantum architecture) ✅ | 10,000 TPS = fastest secp256k1 HNDL archive accumulation in EVM history ❌ |
| Consensus key security | Post-quantum architecture ✅ | MonadBFT validators use secp256k1 — on-chain HNDL archive from registration ❌ |
| Smart account support | ERC-4337 account abstraction ✅ | ERC-4337 compatible — but EOA secp256k1 root authority unchanged ⚠️ |
| PQC migration roadmap | Live at presale — NIST FIPS 203/204/205 ✅ | No published PQC migration plan (Oct 2026) ❌ |
| Presale / stage | Live presale · $662K+ raised · 186+ media mentions | Mainnet live · MON token tradeable |
| TGE | Q2 2026 | Launched 2025 |
| Supply | 1.5 billion tokens | 10 billion MON tokens |
| Throughput | ERC-4337 smart account architecture | 10,000 TPS (parallel EVM) — fastest EVM-compatible L1 |
| EVM compatibility | Smart account layer | Full EVM compatibility — all Solidity/Vyper/tooling works unchanged |
The High-TPS HNDL Archive Acceleration Problem
The Harvest-Now-Decrypt-Later (HNDL) threat is well understood in the context of existing EVM chains: every transaction broadcasts the sender's secp256k1 public key permanently to the on-chain archive. A future CRQC adversary runs Shor's algorithm on these public keys to recover private keys retrospectively.
What is less understood is how throughput directly scales the severity of the HNDL threat. Monad changes this calculation fundamentally:
Ethereum averages approximately 15–33 TPS. Monad targets 10,000 TPS — approximately 300–670× Ethereum's throughput. Every transaction is a secp256k1 public key exposure event. At Monad's peak throughput, the chain can expose more wallet public keys in a single day than Ethereum exposed in its first two years of operation. The HNDL archive that a future CRQC adversary could harvest from Monad grows at an unprecedented rate — proportional to Monad's adoption velocity multiplied by its TPS advantage.
This creates a compound problem: Monad's viral testnet adoption (3.5 million wallets in the first month) combined with its mainnet throughput capacity means the aggregate secp256k1 public key exposure surface scales faster than any prior EVM deployment in history. Every Monad user who sends a transaction — a swap, a bridge, an NFT mint, a game action — permanently adds their wallet public key to the HNDL archive. At 10,000 TPS, even brief periods of high load produce dense key archives that would take a CRQC adversary significant effort to process, but provide extraordinary economic return.
The Parallel Execution Irremediability Factor
Monad's parallel execution engine processes multiple transactions simultaneously, finalising blocks every 1 second. This 1-second finality means that every HNDL archive entry is irrevocably on-chain within 1 second of broadcast — faster than any prior EVM chain. There is no pending-transaction grace period during which a user might retract a broadcast before their public key is finalised. Monad's throughput and speed together create the most rapidly-growing, most rapidly-irremediable secp256k1 HNDL archive in EVM history.
Monad Quantum Exposure Vectors
1. EOA secp256k1 HNDL Archive at 10,000 TPS
Every Monad wallet that sends any transaction permanently exposes its secp256k1 public key. At 10,000 TPS, Monad accumulates the densest secp256k1 HNDL archive in EVM history. A CRQC adversary batch-processes every harvested public key to recover private keys — enabling retrospective sweep of all historical Monad wallets, including those of early adopters, ecosystem funds, team wallets, and protocol treasuries.
2. MonadBFT Validator secp256k1 Consensus Key Forgery
MonadBFT validators sign consensus votes and block proposals with secp256k1 keys registered on-chain from genesis. A CRQC adversary recovering 33%+ of validator stake-weighted keys executes a liveness attack halting the chain. Recovering 67%+ enables full consensus forgery: the adversary signs adversarial block proposals that all honest validators accept as valid, enabling double-spend attacks and chain-wide state manipulation. All validator keys are permanently in the HNDL archive from registration.
3. Foundation + Team Treasury secp256k1 Drain
Monad raised $225 million at a $3 billion valuation. Foundation, team vesting, investor allocation, and ecosystem fund admin wallets are all secp256k1 EVM accounts whose public keys are on-chain since genesis. These are concentrated high-value low-churn wallets — the highest-priority CRQC targets by economic value density. A single CRQC recovery of a foundation or team multisig key enables drain of the entire treasury or blocking of the vesting schedule.
4. Protocol Upgrade Proxy Admin Key Forgery
Monad's core protocol contracts (bridge, staking, governance modules) use proxy upgrade patterns with secp256k1 admin multisig keys. These admin keys are on-chain from deployment. A CRQC adversary recovering threshold admin keys forges a malicious protocol upgrade pointing bridge withdrawals or staking rewards to adversary-controlled addresses. Monad's 1-second block time means a malicious upgrade can be executed and finalised faster than any prior EVM chain's governance can detect.
5. ERC-4337 Smart Account Paymaster Key Compromise
Monad supports ERC-4337 account abstraction. Paymaster contracts that sponsor gas fees for users are controlled by secp256k1 EOA admin keys. A CRQC adversary recovering a paymaster admin key can drain the paymaster deposit, execute malicious UserOperations funded by the paymaster's stake, or grief users by permanently disabling gas sponsorship for dependent applications. ERC-4337 improves UX but does not remove the secp256k1 key at the root authority layer.
6. Governance Circular Paradox
Any Monad PQC migration proposal must pass governance — and governance votes are signed with the exact secp256k1 keys being replaced. A CRQC adversary who has recovered whale voter keys can forge indefinitely blocking governance votes, permanently preventing any PQC migration referendum from reaching threshold. The migration mechanism is self-referentially dependent on the security of the keys it seeks to replace.
Monad CRQC Attack Cascade — 5 Steps
-
1
HNDL Harvest (Accelerated — Monad Testnet Feb 2025 → Oct 2026 + ongoing)
Adversary archives all secp256k1 public keys broadcast on Monad testnet (3.5M+ wallets in month 1) and mainnet at up to 10,000 TPS. Key surface types: EOA wallet secp256k1 (all user transactions); MonadBFT validator secp256k1 consensus keys (on-chain from genesis); foundation/team/investor treasury secp256k1 multisig keys; protocol upgrade proxy admin secp256k1 keys; ERC-4337 paymaster admin secp256k1 keys; ecosystem protocol (DEX, lending, bridge) deployer/admin keys. At sustained 10,000 TPS, the archive grows at ~864 million transactions per day — the fastest secp256k1 archive accumulation rate in EVM history.
-
2
Priority Queue Construction (Highest Return per CRQC Cycle)
Tier 1: MonadBFT top validators by stake weight (67%+ threshold = consensus forgery, highest chain-control value). Tier 2: Foundation + team treasury multisig admin keys (concentrated high-value, low-churn). Tier 3: Protocol upgrade proxy admin keys (enables malicious contract upgrades). Tier 4: Major DeFi protocol admin keys (DEX LPs, lending vaults, bridges). Tier 5: ERC-4337 paymaster admin keys. Tier 6: Whale MON holder EOAs by balance. Tier 7: Batch remaining user EOAs by balance descending.
-
3
Shor's Algorithm secp256k1 ECDLP Recovery
CRQC runs Shor's algorithm against each harvested secp256k1 public key. secp256k1 ECDLP recovery requires approximately 512 logical (fault-tolerant) qubits. The same Shor's circuit template applies uniformly to every secp256k1 public key in the archive — validator keys, treasury multisig keys, user EOAs — enabling batch parallelisation across multiple CRQC units or sequential processing down the priority queue.
-
4
Multi-Vector Simultaneous Execution
With recovered keys in hand: (a) MonadBFT consensus forgery — adversary signs block proposals accepted by all honest validators; (b) Foundation/team treasury drain — adversary executes secp256k1-signed outbound transfers before multisig co-signers can respond; (c) Protocol upgrade forgery — malicious upgrade proposal signed by recovered admin keys redirects bridge/staking funds to adversary addresses; (d) Governance blocking — adversary forges PQC migration blocking votes from recovered whale keys, preventing any on-chain remediation; (e) Batch EOA wallet sweeps — automated drain of MON and any ERC-20/NFT tokens from all compromised wallets simultaneously. Monad's 1-second finality means each adversarial action is irrevocable within 1 second of execution.
-
5
Permanent Irremediability
MonadBFT finalised blocks are cryptographically irreversible — no rollback mechanism exists for finality-confirmed transactions. The HNDL archive spanning Monad testnet and mainnet history cannot be erased from any node. Treasury drains, protocol upgrades, and batch wallet sweeps are complete before governance can convene. The governance circular paradox means adversary-forged blocking votes prevent any on-chain PQC migration vote from passing. Every additional Monad user and transaction before migration adds to the permanently compromised key set.
Monad PQC Migration — 5 Structural Blockers
| Blocker | Why It Blocks Migration |
|---|---|
| No NIST FIPS PQC standard for EVM EOA secp256k1 | As of October 2026, no NIST FIPS standard defines a PQC replacement for secp256k1 in EVM accounts. Ethereum has no accepted EIP for PQC account key types. Monad inherits this structural absence of any standardised migration path. |
| HNDL archive permanence post-migration | Any keys that signed transactions before migration have permanently broadcast their secp256k1 public keys to the on-chain archive across every full node and archive node. Migration to PQC keys does not erase historical public keys — old addresses remain harvested and recoverable by a future CRQC, regardless of when migration occurs. Early Monad users who migrated are still vulnerable through their pre-migration historical transactions. |
| MonadBFT validator key rotation race condition | Rotating 100+ validator secp256k1 keys to PQC while maintaining continuous BFT consensus requires coordinated key rotation without a liveness gap. Any rotation window in which some validators have migrated and others have not creates a mixed-key-set consensus state not covered by the current MonadBFT protocol specification. The protocol would require a hard fork to support PQC key types in consensus messages. |
| Ecosystem-wide voluntary user key migration | Millions of Monad EOA holders — including all testnet participants (3.5M+ wallets) — would need to voluntarily migrate to new PQC key pairs. There is no mechanism to force key migration in an EVM chain. Any unmigrated wallet retains its secp256k1 key exposure. Achieving meaningful migration coverage across a large user base before a CRQC arrives is structurally uncertain. |
| Governance circular paradox | PQC migration governance votes are signed with the secp256k1 keys being replaced. An adversary with recovered whale voter keys can forge blocking votes indefinitely, preventing any migration governance proposal from reaching approval threshold. The migration mechanism is self-referentially dependent on the security of the keys it seeks to replace. |
Monad Genuine Strengths (Fair Assessment)
A rigorous comparison acknowledges Monad's real innovations. These are substantial:
Pipelined Parallel EVM Execution
Monad's optimistic concurrency-controlled parallel execution is a genuine breakthrough in EVM throughput — the first EVM-compatible chain to achieve 10,000 TPS without sacrificing EVM opcode compatibility or developer tooling.
MonadBFT — Single-Slot Finality
MonadBFT delivers BFT finality in 1 second, compared to Ethereum's ~12-second slots and multi-slot finality (~15 minutes for full probabilistic finality). This is a meaningful UX and cross-chain bridging improvement.
Zero Developer Friction
Full EVM compatibility means every Solidity/Vyper contract, every Hardhat/Foundry workflow, every MetaMask/WalletConnect integration works on Monad unchanged. The developer migration cost from Ethereum is essentially zero.
Tier-1 VC Backing + $225M Raised
Paradigm, Electric Capital, Greenoaks, and Coinbase Ventures at $3 billion valuation (April 2024) represents the strongest VC backing of any new L1 in the 2024–2026 cohort. Runway and ecosystem fund are substantial.
MonadDb Custom Storage
MonadDb replaces LevelDB/RocksDB with a custom Patricia trie optimised for Monad's parallel execution patterns and async I/O. State access latency is significantly lower, enabling the high TPS without hardware requirements that exclude consumer nodes.
3.5M+ Testnet Wallets in Month 1
Monad's testnet attracted over 3.5 million unique wallets in its first month — one of the strongest community mobilisation results for any new EVM chain on record. Network effect and community engagement are genuine competitive moats.
Monad's technical strengths and its quantum vulnerability are directly coupled. Its 10,000 TPS throughput advantage — the feature that makes it the most compelling new EVM chain — is simultaneously the mechanism that accelerates secp256k1 HNDL archive growth to unprecedented rates. The better Monad succeeds at its mission, the larger the HNDL archive grows, and the more valuable the aggregate CRQC target becomes. Monad's quantum security posture degrades proportionally with its adoption success.
BMIC Post-Quantum Architecture
BMIC implements the three NIST FIPS standards for post-quantum cryptography ratified in August 2024:
| Standard | Algorithm | Type | Security Basis | BMIC Use |
|---|---|---|---|---|
| FIPS 203 | ML-KEM (CRYSTALS-Kyber) | Key Encapsulation | Module Learning With Errors (MLWE) — lattice-based | Quantum-safe key exchange |
| FIPS 204 | ML-DSA (CRYSTALS-Dilithium) | Digital Signature | Module Learning With Errors (MLWE) — lattice-based | Quantum-safe transaction signing |
| FIPS 205 | SLH-DSA (SPHINCS+) | Digital Signature (stateless) | Hash function security — no algebraic structure | Backup signature scheme |
None of these schemes rely on elliptic curve discrete logarithm or integer factorisation problems. No known quantum algorithm provides more than quadratic speedup (Grover's) against the security primitives they employ — and NIST's security level selections account for Grover's speedup explicitly. BMIC also implements ERC-4337 account abstraction, enabling smart account wallets that are not bound to the secp256k1 key model.
The HNDL threat operates in the present, not when a CRQC arrives. Adversaries harvest public keys today and decrypt private keys retrospectively when quantum hardware matures. Quantum-safe architecture implemented at the presale stage means BMIC token holders' keys were never exposed to the secp256k1 HNDL vulnerability — regardless of when a CRQC becomes available. "We'll upgrade when quantum computers arrive" is not a valid security strategy against HNDL.
Join the BMIC Presale — Quantum-Safe from Day One
BMIC implements NIST FIPS 203, 204, and 205 post-quantum cryptography at the presale stage — not as a future roadmap item. $662K+ raised, 186+ media mentions, TGE Q2 2026.
Get BMIC at Presale →DYOR — This is not investment advice. Cryptocurrency investments carry significant risk.
Frequently Asked Questions
Related BMIC Comparisons
BMIC: Built Quantum-Safe from the Presale
NIST FIPS 203 · FIPS 204 · FIPS 205 · ERC-4337 · TGE Q2 2026 · $662K+ raised · 186+ media mentions
Join the BMIC Presale →DYOR · Not financial advice · bmic.ai