BNB CHAIN · L1 · STAGE 1 ACKNOWLEDGED · QRI 19 v3.1.0 methodology

BNB Chain has the highest hard-fork cadence in the L1 set under evaluation (Pascal, Lorentz, Maxwell, Fermi, Osaka/Mendel, five upgrades in 12 months) and zero core-team PQC commitment. The chain's quantum posture is shaped entirely by an unmerged community PR (BEP-575 Falcon, Draft since May 2025).

inLinkedIn ↷Audit access ⇆Compare Verified 2026-05-01

Summary

BNB Chain (scoring BSC as the active L1 after the Beacon Chain sunset 2024-11-19) scores QRI 19, Band 2 Acknowledged, Migration Stage 1. BSC runs ECDSA secp256k1 (EVM transaction signatures, validator block-proposal signing under Parlia), BLS12-381 with the BLS_SIG_BLS12381G2_XMD:SHA-256_SSWU_RO_POP_ scheme (BEP-126 fast finality vote signing and aggregated attestation), Keccak-256 (state/tx hashing per EVM), and SHA-256. Every signature primitive currently in production is quantum-vulnerable. BEP-575 (Falcon Post-Quantum Signatures) is an OPEN Draft pull request opened 2025-05-19 by an external contributor, proposing a Falcon-512 / Falcon-1024 verification precompile and an opt-in Falcon-secured validator voting layer; not merged, not authored by BNB Chain core. BEP-CequreX (PR #596) was closed unmerged on 2025-08-05. The 2026 Tech Roadmap (published 2026-01-09) makes no PQC commitment. BSC's two strongest assets for migration, small validator set (21 cabinet + 24 candidate = 45) enabling rapid coordination, and Ethereum-compatibility for inheriting upstream PQ work, are real but unrealised. Mainnet-Traffic cap binds at 5a=0%, Architecture-Execution Gap is 44, supply-chain weak-link cap fires across all 4 vendor tiles. The QRI of 19 reflects current state, not potential.

What the gates say

Gate 1a, Hybrid signature: FAIL , BEP-575 unmerged describes an OR-style dual-signature ECDSA+Falcon window only as a migration window, not a permanent hybrid commitment, and does not specify commit-to-hash-of-both-pubkeys
Gate 1a, Hybrid KEM: FAIL , no documented hybrid PQ KEM on validator transport, RPC TLS, or bridge channels
Gate 1b, Commit-to-hash: COND , no OR-composition documented at production-spec level
Gate 2, Evidence reconstruction: PASS , all sub-scores reconstructible from public artifacts in 48 hours
Gate 3, Primitive naming: PASS , every primitive named with parameter set

Burn-vs-rescue policy on file

Declared option f, Undeclared. Public materials do not address what happens to legacy quantum-vulnerable balances post-migration. Given centralisation and the 2022 Token Hub precedent, a Binance-driven rescue path is the operational base case but is not declared policy.

Seven dimensions

Each dimension scores 0–100 internally; the weighted roll-up produces the QRI.

1 Cryptographic Exposure weight 15% 24 / 100

1a · primitive inventory 12 / 20

BSC publishes its primitives across the staking/consensus docs, BEPs, and the bsc go-ethereum fork. Primitives are named with parameter sets and module paths but do not consolidate into a single cryptography reference page comparable to Aptos/Algorand.

Primitives: ECDSA secp256k1 (EVM transaction signatures, validator block-proposal signing under Parlia) ·

BLS12-381 with BLS_SIG_BLS12381G2_XMD:SHA-256_SSWU_RO_POP_ scheme (BEP-126 fast finality vote signing and aggregated attestation)

· Keccak-256 (state/tx hashing per EVM) · SHA-256 (system-contract hashing surfaces) · Merkle Patricia trie hashing

1b · shor grover pq tag 4 / 20

Tags:

ECDSA-secp256k1 → Shor-break-via-DL-without-pairings
BLS12-381 → Shor-break-via-pairings (consensus fast-finality aggregation)
Keccak-256 → Grover-weaken-128bit
SHA-256 → Grover-weaken-128bit

1c · family diversity 0 / 20

0 PQ-safe families deployed. BEP-575 (Falcon) is an OPEN Draft PR by an external contributor, not merged and not authored by BNB Chain core. BEP-CequreX (PR #596) was closed unmerged on 2025-08-05.

1d · nist security category 0 / 20

No PQ primitive deployed. Falcon proposal in BEP-575 would map to NIST Category 1 (Falcon-512) and Category 5 (Falcon-1024) if accepted. Voided to 0 because no production PQ primitive exists.

1e · implementation quality 8 / 20

Production primitives use libsecp256k1 (ECDSA) and supranational/blst (BLS12-381 aggregation, the same library Ethereum and Aptos consensus rely on). The BSC client is a go-ethereum fork; bnb-chain/bsc inherits geth's cryptographic library provenance and audit history. No formal-verification artifacts published for BSC-specific consensus modifications.

2 Quantum Recovery Exposure weight 10% 22 / 100

Forge subtotal: 16/75 Decrypt subtotal: 6/25

2a · active key exposure 4 / 25

BSC inherits Ethereum-style EOA model, secp256k1 public keys revealed when an account first signs a transaction. BNB Chain hosted the highest daily active users of any chain in 2025 with ATHs of ~31M daily transactions and 58M monthly active users, producing one of the largest revealed-pubkey surfaces in the EVM ecosystem. TVL on BSC was approximately $6.9B in early 2026 per DeFiLlama.

2b · cold key exposure 7 / 25

BSC mainnet genesis September 2020 (~5.5 years operational by May 2026). EVM-style accounts that never signed retain SHA3-derived address indirection and remain quantum-resistant in the cold state, but the share of dormant-yet-unrevealed addresses is small relative to the active surface. Sizable Binance-controlled hot/cold wallet balances are a concentrated cold-key target.

2c · sig long term validity 5 / 25

All historical secp256k1 EOA signatures and all BLS12-381 fast-finality aggregated vote attestations (BEP-126 production since the Plato/Luban hard-fork sequence in 2023) are forgeable post-Shor.

2d · encryption confidentiality hndl 6 / 25

Validator gossip, RPC TLS, and bridge relay channels use standard classical TLS (X25519/ECDHE KEMs, ECDSA/RSA cert chains). No documented hybrid PQ KEM deployment on BSC validator transport or dominant RPC providers (BNB Chain RPC, Ankr, QuickNode, NodeReal, Tatum).

3 Metadata, Anonymity & Confidentiality weight 13% 21 / 100

3a · tx graph visibility 4 / 20

Transparent EVM ledger; identical pseudonymity model to Ethereum mainnet. No native shielded pool. The high transaction count (12-17M daily, ATH 31M) makes graph analysis dense in absolute terms.

3b · rpc mempool concentration 3 / 20

RPC traffic concentrates on Binance-affiliated endpoints and a small set of providers (Ankr, QuickNode, NodeReal, Tatum). Validator set is structurally small, 21 cabinet + 24 candidate = 45 total, making mempool gossip observable to a tight set of actors, with Binance-related operators historically holding multiple cabinet seats.

3c · cross chain bridge correlation 4 / 20

Primary bridges into and out of BSC are LayerZero (omnichain messaging, 150+ networks), Wormhole, Stargate (LayerZero-based), and the legacy Binance Bridge / Token Hub system (also the source of the October 2022 ~2M BNB exploit that triggered an emergency chain halt). All bridges are observable by passive cross-chain indexers.

3d · retroactive de anonymization 6 / 20

BSC has no shielded-pool layer, so the standard Shor-on-secp256k1 + Shor-on-BLS12-381 retroactive risks apply but no additional ring-signature, ElGamal, or zk-SNARK encryption layer exists. KYC linkage from Binance CEX activity to BSC addresses is the primary realistic de-anonymization vector.

4 Migration Architecture weight 10% 49 / 100

4a · crypto agility 8 / 15

BSC is a go-ethereum fork and inherits Ethereum's EVM precompile and hard-fork pathway for adding new cryptographic primitives, BEP-439 already added a BLS12-381 precompile pattern that BEP-575 (Falcon) explicitly cites as its template. The 2026 Osaka/Mendel hard fork (scheduled 2026-04-28) imports EIP-7825 via BEP-652. EIP-7702 (account-code on EOAs) inheritance not yet confirmed merged on BSC.

4b · aa key rotation 8 / 20

BSC inherits ERC-4337 account-abstraction infrastructure that runs on EVM-compatible chains. Native account abstraction primitives in BSC's own validator-key surface are limited; validator keys are ECDSA + BLS, with no on-chain rotation primitive equivalent to Aptos's account::rotate_authentication_key. EIP-7702 inheritance not yet confirmed merged on BSC.

4c · hard fork track record 13 / 15

2025-2026 hard-fork cadence is the highest of any major L1: Pascal, Lorentz (2025-04-29, block-time to 1.5s), Maxwell (2025-06-30, block-time to 0.75s), Fermi (2026-01-14, block-time to 0.45s + fast-finality strengthening), Osaka/Mendel (2026-04-28, 9 BEPs). All shipped on documented timelines without contested forks. The October 2022 Token Hub exploit triggered an emergency chain halt within hours, demonstrating crisis-coordination capacity (also a centralization signal).

4d · hybrid deployment readiness 5 / 15

BEP-575 as drafted explicitly contemplates an OR-style hybrid for governance/voting (dual-signature ECDSA+Falcon windows minimise liveness risk) but is unmerged and authored by an external contributor. The 2026 Tech Roadmap makes no PQC commitment, its priorities are 20,000 TPS, sub-second finality, dual-client (Geth + Reth), parallel execution, and developer middleware. Architectural support for hybrid is plausible (any EVM precompile-based scheme can co-exist with secp256k1) but no AND/OR-hybrid composition with commit-to-hash-of-both-pubkeys is specified.

4e · stateful hash state management 15 / 15

BSC has no stateful-hash scheme deployed or proposed. Falcon (proposed in BEP-575) is stateless. Default 15 applies.

4f · bft aggregation path 0 / 20

BSC uses BLS12-381 aggregated vote attestation in BEP-126 fast finality across the 21 cabinet validators (extended in subsequent BEPs to the full 45-validator set). No published spec, testnet, or mainnet pilot for a PQ aggregation path at consensus.

5 Deployment Execution weight 22% 5 / 100

5a · mainnet pqc traffic pct 0 / 25

0% of BSC mainnet signing traffic uses PQ primitives. BEP-575 is unmerged Draft; no Falcon precompile callable on mainnet.

5b · pqc code in consensus client 0 / 15

No PQ code merged into bnb-chain/bsc (Geth fork) or bnb-chain/reth (Rust client). Code searches against both repositories return zero hits for falcon, dilithium, or post-quantum in cryptographic modules.

5c · validator pqc key adoption 0 / 15

No validator runs a PQ consensus key. The 21-cabinet + 24-candidate set (45 total) all sign with secp256k1 (block proposal under Parlia) and BLS12-381 (BEP-126 fast-finality vote attestation).

5d · published dated milestones 0 / 10

VOIDED to 0 per v3.1 because 5a = 0. The 2026 Tech Roadmap (2026-01-09) does not list PQC as a goal. BEP-575 is a Draft PR with no merger date, no testnet schedule, and no mainnet flag day.

5e · pqc washing delta 5 / 15

BNB Chain core has issued no public PQC commitment as of 2026-05-01, the 2026 Tech Roadmap blog post and Osaka/Mendel announcement contain zero PQC content. Press coverage of the chain's quantum posture is similarly absent. The only PQ-tagged surface is the unmerged BEP-575 PR by an external contributor. Partial credit for not over-claiming, low ceiling because there is nothing to deploy against.

5f · signature footprint multiplier 0 / 20

No PQ signature deployed. BEP-575 cites Falcon-512 ~666-byte signatures and 897-byte public keys against secp256k1's 64-byte signatures and 33-byte compressed pubkeys, a ~10-11× raw-byte multiplier for signatures and ~27× for pubkeys, plus Falcon-1024 at ~1,280 bytes (~20×). Voided because no mainnet deployment exists.

6 Supply Chain Vendor Readiness weight 22% 6 / 100

6a · wallet 2 / 25

Top-3: Binance Web3 Wallet, Trust Wallet (Binance-affiliated history, now operates independently with ~200M downloads), MetaMask. None has published a PQ key-derivation or PQ signing roadmap on BSC as of 2026-05-01.

6b · bridge 1 / 25

Top-3: LayerZero (post-Token-Hub-sunset omnichain default), Wormhole, Stargate (LayerZero-based liquidity layer). None publishes a PQ aggregation-key, PQ-validator, or hybrid-KEM transport roadmap for BSC routes.

6c · custodian 2 / 25

Top-3: Ceffu (rebranded from Binance Custody in 2023; institutional-grade MPC custody, ISO 27001/27701, SOC 1/2), BitGo, Fireblocks. Ceffu's public materials describe MPC and multi-approval frameworks but do not publish a post-quantum cryptography roadmap. BitGo and Fireblocks publish forward-looking PQ statements (NIST-aligned hybrid pilots) but no BSC-specific PQ key-management product is deployed.

6d · rpc hsm tee infra 1 / 25

Top-3 RPC: BNB Chain official RPC, Ankr, QuickNode (NodeReal and Tatum also material). No PQ-TLS / hybrid-KEM termination on public BSC RPC endpoints. HSM/TEE chain not documented as PQ-pilot anywhere in the BSC stack.

7 Governance & Coordination weight 8% 40 / 100

7a · validator stake distribution 5 / 20

45 validators total (21 active Cabinet rotating per epoch + 24 Candidate with smaller block-production probability). Validator set roles reset every 24h based on staking ranking. Nakamoto coefficient is structurally low, ChainSpect dashboard shows BSC at the centralised end of the L1 distribution. Single execution client (geth-fork bsc) until 2026; the Reth Rust client is being introduced as a second client for diversity.

7b · upgrade cadence under pressure 16 / 20

Highest hard-fork cadence in the L1 set under evaluation. Pascal + Lorentz (April 2025) → Maxwell (June 2025) → Fermi (January 2026) → Osaka/Mendel (April 2026), four-to-five mainnet upgrades inside 12 months. October 2022 Token Hub exploit response (chain halt + governance-driven recovery) demonstrated crisis-pace coordination.

7c · named coordination lead 12 / 20

BNB Chain core team operates the BEP process via the bnb-chain/BEPs repository; the Tech Roadmap 2026 was published under the BNB Chain blog (institutional voice, no individual lead named). Binance is the dominant ecosystem actor. No named PQC lead, no PQC working group charter.

7d · adversarial coordination precedent 7 / 20

October 2022 Token Hub exploit (~$566M attempted, ~$110M extracted) triggered a coordinated emergency chain halt within hours and a follow-up patch hard fork. Demonstrates rapid coordination under pressure but the precedent is a bridge-exploit response, not a coordinated cryptographic primitive change under active attacker presence.

7e · canary tripwire mechanism 0 / 20

No canary, honeypot, rate-limited spending rule, or in-consensus cryptographic tripwire documented for BSC.

X + Y vs Z, when does the math turn against you?

v3.1 demotes the X+Y vs Z timing test to a secondary signal, the headline output is Migration Stage. The timing test still answers the question: can this chain finish migrating before the threat lands?

X, signature shelf life

5–10 years

Y, migration time

5–8 years to Stage 5 (lower bound compressed by the strongest L1 hard-fork cadence; upper bound held by absence of core-team PQ commitment and lack of vendor-side roadmaps)

Z10 (10% CRQC year)

2030

Z25 (25% CRQC year)

2035

Verdict

X+Y = 2031–2036, partially Outside risk window vs Z25; Crisis Zone vs Z10

Z-compliance

Outside compliance window at upper bound (2035-2036); deprecation window at lower bound (2031). EU NIS2 / DORA institutional consumers face overlay deadlines

Source-disagreement disclosure

v3.1 requires every chain card to publish material divergences among authoritative sources, plus the delta-QRI under alternative weighting.

Validator count framing

docs.bnbchain.org states 21 cabinet + 24 candidate = 45; community sources sometimes cite 21 validators as shorthand. The 21/45 figure is the authoritative one.

TVL definitional scope

DeFiLlama 2026-04 BSC TVL (~$6.9B) versus older 2025 ecosystem-wide figures (up to $17.1B) reflects a definitional difference (TVL vs ecosystem-wide value across DeFi/CeDeFi/wallet balances).