BMIC Presale — NIST Quantum-Safe Crypto Buy BMIC at $0.0528542 →

BMIC vs NEAR Protocol (NEAR) 2026 —
The Named-Account Chain Where 6+ Years of Harvested ed25519 and secp256k1 Keys Threaten Every Wallet, Validator, and Aurora Bridge

Updated September 2026 · BMIC Research · DYOR

NEAR Protocol uses ed25519 for native wallet accounts and secp256k1 for Aurora EVM compatibility — both are elliptic curve schemes broken by Shor's algorithm. With a named account system that maps human-readable identities to on-chain ed25519 keys, a 6+ year HNDL archive, and no NIST FIPS PQC roadmap published, NEAR carries compounding quantum debt across both its native and EVM layers. This page examines each exposure in plain technical terms.

Buy BMIC — Quantum-Safe from Day One
⚛️

Research Verdict — September 2026

NEAR Protocol is a technically ambitious sharded L1 with a strong DeFi and gaming ecosystem. Its ed25519 named account system is a genuine UX innovation for self-custody. However, ed25519 is based on ECDLP — broken by Shor's algorithm with the same efficiency as secp256k1. The Aurora EVM layer adds a second secp256k1 harvest surface. The combined 6+ year HNDL archive from both key types, the named account system that explicitly links account value to public keys, and the absence of any NIST FIPS PQC migration roadmap mean NEAR's quantum debt compounds with every block. BMIC implements NIST FIPS 203/204/205 from genesis. DYOR.

Head-to-Head: BMIC vs NEAR Protocol (NEAR)

Criterion BMIC NEAR Protocol (NEAR)
Native signature algorithm ML-DSA / Dilithium (NIST FIPS 204) ed25519 ECDSA (Shor-vulnerable ECDLP)
EVM compatibility ERC-4337 on PQC infrastructure Aurora EVM: adds secp256k1 as second vulnerable surface
Key encapsulation ML-KEM / Kyber (NIST FIPS 203) ECDH on Curve25519 / secp256k1 (quantum-vulnerable)
HNDL archive window None — quantum-safe from genesis 6+ years (October 2020 → present; 2 key types)
Account model PQC key pairs from genesis Named accounts: human-readable IDs → ed25519 public keys (named = identifiable HNDL targets)
Multi-key accounts PQC multi-key infrastructure Multiple ed25519 FullAccess + FunctionCall keys per account = multiple harvest targets per user
Bridge security PQC key management from genesis Aurora rainbow bridge: secp256k1 admin keys + ed25519 relayer keys
Governance model Post-quantum key infrastructure Validator ed25519 consensus — governance circular paradox
PQC migration roadmap NIST FIPS 203/204/205 — shipped None published as of October 2026
Mainnet since PQC from day one October 2020 (6+ year HNDL archive)
Presale / entry price $0.0528542 — presale live Publicly traded (no presale)
Quantum risk rating ✅ Quantum-safe 🔴 High — dual key surfaces, 6+ yr HNDL archive, named-account identifiability, no PQC roadmap

Two Critical NEAR Quantum Misconceptions

Misconception 1: "NEAR uses ed25519, not secp256k1 — it's more secure against quantum attacks"

Ed25519 (EdDSA on Edwards25519 / Curve25519) is a genuine improvement over secp256k1 for classical security: it is faster, has better side-channel resistance, and avoids certain implementation pitfalls of ECDSA. However, both ed25519 and secp256k1 are elliptic curve signature schemes whose security relies on the Elliptic Curve Discrete Logarithm Problem (ECDLP). Shor's algorithm solves ECDLP efficiently on any elliptic curve. The curve choice (Curve25519 vs secp256k1) does not affect Shor's algorithm applicability — it determines the classical security level and implementation properties, not the quantum security level. Ed25519 is quantum-vulnerable for the same reason secp256k1 is quantum-vulnerable: both rely on ECDLP.

Misconception 2: "NEAR's sharding (Nightshade) distributes risk and reduces quantum exposure"

Nightshade sharding is a horizontal scalability architecture — it distributes transaction processing across multiple shard chains to increase throughput. It has no effect on the underlying ed25519 cryptographic primitive used by every validator and account key on every shard. Sharding distributes computational load; it does not distribute cryptographic risk. A CRQC adversary harvesting ed25519 public keys from the NEAR blockchain collects keys from all shards simultaneously. The validator set for each shard uses ed25519 consensus keys. Sharding into more components with more key surfaces adds more HNDL targets, not fewer.

NEAR Key Architecture: 8 Quantum-Exposed Surfaces

Component Key Algorithm Function CRQC Risk
Native named accounts (alice.near) ed25519 (Curve25519) Token transfers, staking, contract deployment, governance 🔴 Critical — 6+ yr HNDL archive; named accounts identify high-value targets
Aurora EVM accounts secp256k1 ECDSA Ethereum-compatible dApp interaction, Aurora DeFi 🔴 Critical — second independent key surface; Shor-vulnerable
Validator consensus keys ed25519 Block signing, Nightshade shard consensus, finality 🔴 Critical — consensus forgery, chain reorg across all shards
Aurora rainbow bridge admin secp256k1 ECDSA Ethereum↔NEAR bridge: admin key controls bridge contract upgrades and emergency pause 🔴 Critical — forged admin transactions draining bridge locked assets
Multi-key FunctionCall keys ed25519 Restricted permission keys for specific contract methods; multiple keys per account 🟠 High — each key is an independent harvest target; recovery enables specific contract-level actions
Staking contract admin keys ed25519 Staking pool admin authority: reward distribution, unstake timing, fee parameters 🟠 High — forged admin transactions redirect staking rewards or force premature unstaking
Rainbow bridge relayer keys ed25519 NEAR-side relayer signing for cross-chain message relay 🟠 High — forged relay messages bypass IBC-style authentication
DeFi protocol admin keys (Ref Finance, Burrow, etc.) ed25519 Protocol upgrade authority, parameter controls for major NEAR DeFi protocols 🟡 Medium — contract upgrade forgery, fee manipulation, liquidity redirect

The Named Account Quantum Risk: Identifiable HNDL Targets

NEAR Protocol's named account system (alice.near, exchange.near, dao.near, treasury.near) maps human-readable identifiers to ed25519 key pairs published on-chain. This UX innovation — which genuinely reduces the self-custody barrier — creates a unique quantum risk not present in hash-based address systems.

⚠️ Named accounts are a pre-built CRQC priority queue

In most blockchains (Ethereum, Bitcoin), the value of an address can only be inferred by checking the balance — the address itself is a hash that reveals nothing about the owner or value. NEAR named accounts explicitly signal value through the name itself. An adversary with a CRQC building a harvest priority queue does not need to guess which public keys correspond to high-value targets: "exchange.near", "treasury.near", "dao.near", "foundation.near" are immediately identifiable as high-priority targets. The 6+ year HNDL archive from October 2020 includes every named account ever registered, their associated ed25519 public keys, and their transaction history confirming value levels.

NEAR Quantum Exposure Map

🔴 HNDL Archive — 6+ Years, Dual Key Types

NEAR mainnet launched October 14, 2020. Every ed25519 named account key and every Aurora secp256k1 account key broadcast on-chain since then forms an irremediable harvest archive. Two distinct Shor's algorithm target pools: Curve25519 ECDLP and secp256k1 ECDLP. Both pools have been accumulating for 6+ years.

🔴 Named Account — Identifiable Priority Queue

Human-readable account names signal value without on-chain balance lookup. Known exchange accounts, DAO treasuries, foundation wallets, and protocol admin named accounts are identifiable as the highest-priority CRQC targets from public NEAR chain data alone, without any balance queries. The named account system converts the HNDL archive from anonymous addresses into a labelled priority queue.

🔴 Aurora Rainbow Bridge Admin Drain

The Aurora rainbow bridge holds locked ETH and ERC-20 assets on Ethereum side, mirrored as NEAR-side tokens. Bridge admin keys are secp256k1 ECDSA. CRQC recovery enables forged admin upgrade transactions draining the Ethereum bridge contract, or forged emergency pause/unpause operations redirecting bridge asset flows — with cryptographically valid signatures.

🔴 Validator Consensus Key Forgery (All Shards)

Nightshade shard validators sign block proposals and finality messages with ed25519 keys. CRQC recovery of top validator keys enables forged block signatures across the shard chain, equivocation attacks producing conflicting finality proofs, and shard reorganisation. Because stake is distributed across a finite validator set, fewer recovery operations are required than a more distributed consensus system.

🟠 Multi-Key Account — Multiple Harvest Targets

NEAR accounts support FullAccess keys and multiple FunctionCall keys with restricted permissions for specific contracts or methods. Each key is an independent ed25519 key pair published on-chain when used. A single NEAR account can expose 5+ separate ed25519 public keys, each recoverable independently, each enabling specific account actions — a single account multiplied into multiple CRQC recovery operations.

🟠 NEAR Governance Circular Paradox

NEAR protocol upgrades require validator supermajority approval via ed25519-signed block proposals. Any on-chain PQC migration proposal must pass through this ed25519-governed mechanism. A CRQC adversary with recovered validator keys can block any legitimate PQC migration or approve malicious protocol changes. Escape requires a coordinated off-chain hard fork with no scheduled mechanism as of October 2026.

🟠 Staking Contract Admin Key Redirection

NEAR staking pools (Ref Staking, Meta Staking, etc.) have ed25519 admin authority over reward distribution timing, staking fee parameters, and unstaking queues. CRQC recovery of pool admin keys enables forged administrative actions redirecting delegator rewards, manipulating fee parameters to drain staking yield, or forcing premature unstaking to create market pressure.

🟡 DeFi Protocol Admin Key Forgery

Major NEAR DeFi protocols (Ref Finance AMM, Burrow lending, Trisolaris DEX) have ed25519 admin keys controlling upgrade authority and protocol parameters. CRQC recovery enables forged upgrade transactions replacing protocol contracts with malicious implementations, redirecting liquidity pool assets, or manipulating lending parameters to trigger mass liquidations.

5-Step CRQC Cascade on NEAR Protocol

  1. Step 1 — HNDL Harvest (6+ Years, Two Key Types)

    Passive collection of all ed25519 public keys (named accounts, validators, staking pools, FunctionCall keys, bridge relayers, DeFi admin keys) and all Aurora EVM secp256k1 public keys broadcast on NEAR since October 2020. Named accounts provide a pre-built value signal: exchange.near, treasury.near, dao.near keys are indexed as highest-priority targets without balance lookup.

  2. Step 2 — Priority Queue Construction

    Rank targets by impact and identifiability: Aurora rainbow bridge admin keys (controls locked ETH/ERC-20 assets) → validator consensus keys (controls shard chain finality) → NEAR Foundation + governance whale wallets (controls protocol direction) → DeFi protocol admin keys (Ref Finance/Burrow/Trisolaris) → staking pool admin keys → high-value named accounts (identifiable by name) → Aurora EVM high-balance accounts → general user accounts.

  3. Step 3 — Dual-Algorithm Shor Recovery

    Apply Shor's algorithm to ed25519 (Curve25519 ECDLP) and secp256k1 ECDLP targets in parallel. Each algorithm instance operates independently. Recovery time per key: minutes to hours depending on CRQC scale. Full FullAccess key recovery yields complete account control. FunctionCall key recovery yields targeted contract-level authority without triggering FullAccess alerts.

  4. Step 4 — Multi-Vector Simultaneous Attack

    Execute coordinated attack across all recovered keys: (a) Forge Aurora bridge admin secp256k1 signatures draining locked ETH and ERC-20 assets from the Ethereum bridge contract; (b) Forge validator ed25519 consensus signatures across shards to control block production; (c) Forge governance whale wallet signatures blocking any emergency PQC response; (d) Forge DeFi protocol admin transactions replacing contract implementations; (e) Forge staking pool admin transactions redirecting delegator rewards; (f) Execute named account wallet drains in parallel using recovered FullAccess keys. All actions carry cryptographically valid signatures.

  5. Step 5 — Permanent Irremediability

    The NEAR governance circular paradox prevents on-chain PQC migration approval — the validator consensus mechanism uses the same compromised ed25519 keys. Emergency response requires an off-chain hard fork. The 6+ year HNDL archive from both the native chain and Aurora EVM layer is permanent, irremediable, and growing with every block. Named account associations — once published — cannot be retroactively removed from the public ledger.

5 NEAR Protocol PQC Migration Blockers

Blocker Detail Status (Sep 2026)
No NIST FIPS PQC migration roadmap NEAR Protocol has published no public roadmap for migrating native account keys or Aurora EVM keys to NIST FIPS 203/204/205 algorithms as of October 2026. No EIP-equivalent or NEAR Improvement Proposal addressing PQC migration has been finalised. 🔴 No ETA
Named account re-keying — no forced mechanism Every named account holder must generate a new PQC key pair and replace their ed25519 full-access key manually. No forced migration mechanism exists. Inactive accounts with significant balances (exchange wallets, long-term holders) may never be re-keyed, leaving their ed25519 keys permanently harvestable. 🔴 No mechanism
Multi-key account complexity Each NEAR account can have multiple FullAccess and FunctionCall keys. A single account migration requires replacing every individual key pair with a PQC alternative. DApps with hardcoded FunctionCall key dependencies would break on re-keying, requiring coordinated protocol upgrades across the NEAR dApp ecosystem simultaneously. 🔴 No coordination path
Aurora EVM secp256k1 independent migration Aurora's secp256k1 key system is an independent dependency from NEAR native accounts. Migration requires Aurora-specific protocol changes aligned with any future Ethereum EVM PQC standard (no finalised Ethereum PQC EIP as of October 2026) and separate user re-keying for Aurora-side accounts. 🔴 No Ethereum PQC EIP finalised
6+ year HNDL archive — permanent All ed25519 and secp256k1 public keys broadcast on the NEAR chain since October 2020 are permanently on the public blockchain. The combined HNDL archive from both key types grows every block and cannot be retroactively deleted regardless of any future migration. 🔴 Irremediable

BMIC: NIST FIPS 203/204/205 — No HNDL Archive

NIST FIPS 203 — ML-KEM (CRYSTALS-Kyber)

Module lattice-based key encapsulation mechanism. Replaces ECDH on Curve25519 / secp256k1 for key agreement. Security based on the Module Learning With Errors (MLWE) problem — no known efficient quantum algorithm.

NIST FIPS 204 — ML-DSA (CRYSTALS-Dilithium)

Module lattice-based digital signature algorithm. Replaces ed25519 and secp256k1 ECDSA for transaction signing. Security based on MLWE and Module Short Integer Solution (MSIS) — no known efficient quantum algorithm.

NIST FIPS 205 — SLH-DSA (SPHINCS+)

Stateless hash-based signature scheme. Fallback algorithm with security reducible purely to collision resistance of hash functions — independent of lattice assumptions, providing defence in depth against both classical and quantum adversaries.

Why "no HNDL archive" is structurally different from "will migrate later"

BMIC's quantum-safe status is not a promise to migrate later — it is the absence of any harvest target from genesis. There are no ed25519 or secp256k1 public keys on the BMIC ledger for a CRQC to collect. NEAR's 6+ year HNDL archive from both its native ed25519 keys and Aurora EVM secp256k1 keys cannot be retroactively removed. Even a perfect future migration of NEAR accounts to PQC keys cannot delete the historical public keys already on the permanent blockchain record. The HNDL risk is baked in permanently for any chain that used ECDLP-based cryptography before migration — including NEAR.

NEAR Protocol's Genuine Strengths (Independent of Quantum Posture)

✅ Human-Readable Named Accounts

alice.near replaces 0x3f... — a genuine UX innovation reducing the self-custody barrier for new users entering crypto.

✅ Nightshade Sharding

Horizontal scalability via Nightshade sharding allows NEAR to process high transaction volumes across multiple shard chains simultaneously — a genuine L1 scalability solution.

✅ Aurora EVM Compatibility

Ethereum developers can deploy Solidity contracts on Aurora without modification, giving NEAR access to the entire Ethereum dApp ecosystem without a rewrite.

✅ Near-Zero Transaction Fees

NEAR transaction fees are fractions of a cent — enabling micro-transaction use cases, gaming, and social applications that are economically infeasible on higher-fee chains.

✅ NEAR Foundation Grants

NEAR Foundation's developer grants programme has funded hundreds of projects — one of the most active grant programmes among L1 blockchains with a track record since 2020.

✅ 6+ Year Stable Mainnet

NEAR mainnet has operated stably since October 2020 with no major consensus failures — demonstrating production-grade reliability across 6+ years and multiple market cycles.

⚠️ Named account UX advantage creates quantum risk amplifier

NEAR's named account system is simultaneously its most distinctive UX feature and its most distinctive quantum risk amplifier. The identifiability of named accounts — the very feature that makes them useful for human self-custody — makes them a pre-labelled priority target list for CRQC adversaries. alice.near is easier to remember than 0x3f...; it is also easier to identify as a high-value target than an anonymous hash address. The UX benefit and the quantum risk amplification are two sides of the same named-account design choice.

Frequently Asked Questions

Is NEAR Protocol blockchain quantum safe?
No. NEAR Protocol uses ed25519 (Edwards-curve Digital Signature Algorithm on Curve25519) for native wallet accounts. Ed25519 is based on the Elliptic Curve Discrete Logarithm Problem (ECDLP) on Curve25519 — the same class of mathematical problem Shor's algorithm solves efficiently. Additionally, NEAR's Aurora EVM layer uses secp256k1, adding a second quantum-vulnerable key surface. NEAR Protocol has published no NIST FIPS-aligned post-quantum cryptography migration roadmap as of October 2026.
Is ed25519 quantum safe?
No. Ed25519 uses ECDSA on the twisted Edwards form of Curve25519. Like all elliptic curve signature schemes, its security relies on the Elliptic Curve Discrete Logarithm Problem (ECDLP). Shor's algorithm solves ECDLP efficiently on any elliptic curve, including Curve25519. The curve choice affects classical security properties, side-channel resistance, and implementation efficiency — it does not provide quantum resistance. Ed25519 is faster and safer against classical side-channel attacks than secp256k1, but equally broken by a cryptographically-relevant quantum computer (CRQC).
What is the Aurora EVM quantum vulnerability on NEAR?
Aurora is an EVM-compatible layer built on NEAR Protocol. Ethereum-compatible accounts on Aurora use secp256k1 ECDSA — the same key algorithm used on Ethereum mainnet. Users who interact with Aurora dApps broadcast secp256k1 public keys to the NEAR chain, creating a second quantum-vulnerable key surface alongside native NEAR ed25519 accounts. The Aurora rainbow bridge admin keys are also secp256k1. A CRQC adversary builds a HNDL archive from both key types; ed25519 and secp256k1 recovery operations are independent harvest targets.
What is the NEAR governance circular paradox?
NEAR Protocol governance and major upgrades require validator set consensus via ed25519-signed block proposals and community governance via ed25519-signed votes. Any proposal to migrate to post-quantum cryptography must gain validator supermajority approval with ed25519 signatures. A CRQC adversary with harvested validator public keys from the 6+ year HNDL archive can recover validator private keys and forge a supermajority blocking any PQC migration. Escaping requires an off-chain coordinated hard fork with no scheduled mechanism as of October 2026.
What makes NEAR's named account system a special quantum risk?
NEAR's named account system (alice.near, mybusiness.near) maps human-readable names to ed25519 key pairs published on-chain. High-value named accounts — exchanges, DAOs, protocols, known entities — are identifiable in the public HNDL archive without balance lookups. The account name itself signals value, converting the anonymous address archive common on other blockchains into a pre-labelled CRQC priority queue.
How does BMIC protect against quantum attacks?
BMIC implements NIST FIPS 203 (ML-KEM / CRYSTALS-Kyber) for key encapsulation, FIPS 204 (ML-DSA / CRYSTALS-Dilithium) for digital signatures, and FIPS 205 (SLH-DSA / SPHINCS+) as a stateless hash-based fallback. All three standards are based on lattice problems and hash functions — mathematical problems for which no efficient quantum algorithm is known. BMIC carries no HNDL archive because every key on the network uses PQC algorithms from genesis.
What is the BMIC presale price?
BMIC is in presale at $0.0528542 per token. Total supply: 1.5 billion tokens. $662K+ raised. TGE Q4 2026. NIST FIPS 203/204/205. ERC-4337. Visit bmic.ai. DYOR — this is not investment advice.
What are NEAR Protocol's genuine strengths?
NEAR Protocol has real strengths independent of its quantum posture: human-readable named accounts making self-custody more accessible, Nightshade sharding for horizontal scalability, Aurora EVM for Ethereum compatibility, near-zero transaction fees, a thriving DeFi and gaming ecosystem, fast 1-second block times, NEAR Foundation grants programme with strong developer funding, and 6+ years of stable mainnet operation since October 2020.

More BMIC Quantum Comparisons

⚠️ DYOR — This is not investment advice. Cryptocurrency investments carry substantial risk including loss of principal. Quantum computing timelines are uncertain. Cryptographic risk is one factor among many. Nothing on this page constitutes a recommendation to buy or sell any asset. Always conduct your own research before making any financial decision. Visit bmic.ai for the full BMIC technology overview.