MultiversX Secure Proof of Stake uses BLS multi-signatures for 3200+ validators. BLS is pairing-based cryptography — vulnerable to Shor's algorithm. User wallets use secp256k1 ECDSA, also Shor-vulnerable. BMIC deploys NIST FIPS 203, 204, and 205 from genesis.
MultiversX (formerly Elrond) is an adaptive-sharded blockchain that launched its mainnet in July 2020. It uses a custom consensus mechanism called Secure Proof of Stake (SPoS). SPoS selects validator subsets for each shard round using a deterministic random function and aggregates their votes using BLS (Boneh-Lynn-Shacham) multi-signatures.
The network operates across:
Two cryptographic primitives underpin the entire network:
Both primitives are vulnerable to Shor's algorithm on a sufficiently large quantum computer.
BLS is a pairing-based signature scheme operating over bilinear groups — specifically the BLS12-381 pairing-friendly elliptic curve. The hardness assumption underlying BLS is the computational Diffie-Hellman problem (CDH) in pairing-friendly elliptic curve groups.
In MultiversX SPoS, every shard's validators:
A CRQC that derives a validator's BLS private key from its published public key can forge any BLS signature — block headers, shard summaries, cross-shard receipts, staking confirmations — without controlling that validator's hardware or stake.
MultiversX currently has approximately 3,200 validators across its shards. Every one of them has a BLS public key permanently archived on-chain since their registration date.
MultiversX's sharding architecture amplifies the scope of a BLS quantum attack beyond ordinary blockchain wallet theft:
The MetaChain collects, validates, and finalises BLS-signed shard block headers from all three execution shards. It is the ultimate source of truth for cross-shard message delivery, validator staking/unbonding, and reward distribution. A CRQC targeting MetaChain validator BLS keys could:
Cross-shard transactions involve execution on one shard and settlement confirmation on the MetaChain. Every step generates BLS-signed artifacts. The entire lifecycle of every cross-shard transaction — spanning 2026 back to the July 2020 mainnet launch — is preserved on-chain. A future CRQC working through 6 years of archived BLS signatures has complete forensic access to validator key material.
MultiversX rotates validator selection per shard round using a deterministic randomness source. However, rotation does not remove previously published BLS public keys from the chain. Once a validator's BLS public key is on-chain, it remains permanently derivable. A CRQC can queue up attacks on all validators by public key — it does not need real-time access to compromise any given epoch's signers.
The HNDL (Harvest-Now-Decrypt-Later) threat model applies to any blockchain that broadcasts cryptographic material that a quantum computer could later exploit. MultiversX has a significant HNDL exposure:
Two distinct HNDL pools exist:
MultiversX hosts a growing DeFi ecosystem whose users are exposed at the wallet key level:
xEGLD is a liquid staking derivative issued when EGLD is staked via the liquid staking contract. Every stake, unstake, and xEGLD transfer exposes the user's secp256k1 public key on-chain. The contract itself is signed and deployed by an address with an exposed secp256k1 public key.
xExchange (formerly Maiar Exchange) is MultiversX's AMM DEX. Every swap, liquidity add/remove, and farm interaction signs a transaction with secp256k1. DeFi power users who have made hundreds of transactions have contributed hundreds of secp256k1 public key exposures to the HNDL pool.
MultiversX's ESDT token standard (Elrond Standard Digital Token) and NFT framework both rely on secp256k1 wallets. Token issuers, NFT creators, and every marketplace buyer/seller have exposed their secp256k1 public keys. These keys are permanently indexed on MultiversX block explorers.
US National Security Memorandum 10 (NSM-10) mandates that federal agencies migrate to NIST post-quantum cryptography standards. Q3 2026 marks the beginning of active enforcement phases. While NSM-10 is a US federal mandate, its institutional cascade effects extend to the broader crypto market:
As of August 2026, the MultiversX Foundation has published no NIST PQC migration roadmap, no improvement proposal for replacing BLS consensus signatures, and no timeline for replacing secp256k1 user keys.
| Feature | MultiversX (EGLD) | BMIC |
|---|---|---|
| Consensus signature scheme | BLS multi-signature (pairing-based) Shor-Vulnerable | ML-DSA / FIPS 204 Quantum-Safe |
| User wallet signing key | secp256k1 ECDSA Shor-Vulnerable | ML-DSA / FIPS 204 + SLH-DSA / FIPS 205 Quantum-Safe |
| Key encapsulation | None (ECDH-based in TLS layer only) Shor-Vulnerable | ML-KEM / FIPS 203 Quantum-Safe |
| NIST FIPS 203 (ML-KEM) | Not implemented No | Implemented from genesis Yes |
| NIST FIPS 204 (ML-DSA) | Not implemented No | Implemented from genesis Yes |
| NIST FIPS 205 (SLH-DSA) | Not implemented No | Implemented from genesis Yes |
| Validator key quantum risk | 3200+ BLS keys on-chain, all derivable by CRQC Critical | FIPS 204 lattice keys — no known quantum speedup Protected |
| Cross-shard HNDL risk | MetaChain BLS signatures harvestable since July 2020 6+ Years | Genesis deployment; no pre-quantum HNDL window Mitigated |
| Account abstraction | Custom smart contract accounts (secp256k1 underlay) Partial | ERC-4337 with FIPS 204 validation Full |
| NIST PQC migration roadmap | None published as of Aug 2026 None | Deployed at launch — no migration needed Done |
| NSM-10 compliance posture | No NIST alignment — institutional friction risk Non-Compliant | FIPS 203/204/205 deployed — NSM-10 aligned Aligned |
| DeFi ecosystem quantum risk | xEGLD, xExchange, ESDT — all secp256k1 exposed All Layers | FIPS 204 wallet validation — ERC-4337 key isolation Protected |
BMIC implements three NIST post-quantum cryptography standards simultaneously, all deployed from genesis — before TGE — so there is no pre-quantum HNDL window and no secp256k1 legacy debt to retire.
Module Lattice-based Key Encapsulation Mechanism. Replaces ECDH for session key establishment and secure channel setup. Based on the Module Learning With Errors (MLWE) problem — no polynomial-time quantum solution known. Grover's algorithm provides at most a quadratic speedup on symmetric keys (mitigated by 256-bit key sizes).
Module Lattice-based Digital Signature Algorithm. Used to sign BMIC transactions and device attestations. Replaces secp256k1 ECDSA at the transaction validation layer. Deployed in BMIC ERC-4337 smart wallets for UserOperation validation — no bare secp256k1 signature in the transaction envelope.
Stateless hash-based signature scheme. Provides a lattice-independent fallback grounded solely in hash function security — no algebraic structure for Shor's algorithm to exploit. Serves as a defence-in-depth layer: if lattice assumptions were ever weakened, SLH-DSA remains secure.
BMIC uses ERC-4337 account abstraction. UserOperations are validated by the smart contract wallet using ML-DSA (FIPS 204) lattice signatures rather than bare secp256k1 signatures in the transaction envelope. This means:
MultiversX cannot add NIST PQC signatures without a coordinated hard fork replacing BLS at the consensus layer and secp256k1 at the user key layer — across 3,200+ validators, existing staking contracts, and millions of EGLD/xEGLD wallets. BMIC launches with NIST FIPS 203/204/205 from genesis. There is no migration to coordinate, no legacy key pool to deprecate, and no validator re-registration event needed.
No. MultiversX SPoS uses BLS multi-signatures — pairing-based cryptography that Shor's algorithm breaks. User wallets use secp256k1 ECDSA, also broken by Shor's algorithm. Neither layer is quantum-resistant. The MultiversX Foundation has published no NIST FIPS 203/204/205 migration roadmap as of August 2026.
BLS operates over pairing-friendly elliptic curves (BLS12-381). Its security reduces to the computational Diffie-Hellman problem in these groups, which is a specialisation of the discrete logarithm problem. Shor's algorithm solves the discrete logarithm problem efficiently on a quantum computer. A CRQC can derive any BLS private key from its corresponding public key, enabling the forgery of any BLS signature — including MultiversX block attestations and MetaChain finality signatures.
The MetaChain aggregates BLS-signed block headers from all three execution shards. A CRQC compromising MetaChain validator BLS keys could forge cross-shard finality — affecting every cross-shard transaction, staking record, and reward distribution across the entire network. The risk is not limited to individual wallet drains; it is systemic to the entire multi-shard architecture.
Yes. xEGLD interactions sign transactions with secp256k1. Every holder who has staked, unstaked, or transferred xEGLD has exposed their secp256k1 public key on-chain. A CRQC can derive the private key from that public key and drain the wallet. Additionally, the liquid staking contract itself relies on BLS-signed validator confirmations.
BMIC implements all three NIST post-quantum standards finalised in August 2024: FIPS 203 (ML-KEM/Kyber), FIPS 204 (ML-DSA/Dilithium), and FIPS 205 (SLH-DSA/SPHINCS+). These are deployed from genesis — not as a future migration commitment.
Yes. ERC-4337 account abstraction decouples transaction validation from bare secp256k1 signatures. BMIC smart wallets validate UserOperations using ML-DSA (FIPS 204) lattice signatures. The secp256k1 public key is not exposed with every transaction — contrasting sharply with MultiversX's model where every EGLD send permanently exposes the sender's secp256k1 key.
Possibly, but it would require a hard fork replacing BLS at the consensus layer and secp256k1 at the user key layer — coordinating 3,200+ validators, staking contract migrations, and millions of EGLD wallets. As of August 2026, no Improvement Proposal for NIST PQC migration has been published. BMIC deploys NIST FIPS 203/204/205 at genesis, requiring no migration.
This page does not provide investment advice. BMIC is in presale at bmic.ai — over $530,000 raised on-chain, 186+ media features, TGE Q2 2026. MultiversX is an established, liquid blockchain with sharding infrastructure, DeFi, and NFT ecosystems. BMIC carries presale illiquidity risk; MultiversX carries quantum cryptographic risk at the validator consensus (BLS) and user key (secp256k1) layers. DYOR. Never invest more than you can afford to lose.
$530K+ raised on-chain · 186+ media features · NIST FIPS 203/204/205 · TGE Q2 2026. Join the presale before the next phase price increase.
Join the BMIC Presale →DYOR. Not investment advice. Price rises each phase. Never invest more than you can afford to lose.