1 Signature scheme 0/10, weighted 30%
Band 0: Classical signatures only on mainnet, with nothing post-quantum protecting live funds. Short-lived devnets and one-off benchmarks sit here: they demonstrate research rather than something a user can hold keys on.
BNB Chain signs with ECDSA on secp256k1 for EVM compatibility, and nothing post-quantum protects live funds. The ML-DSA work was a test on a non-production network.
source
2 Deployment stage 2/10, weighted 25%
Band 2: Tier 4: Debating.
Tier 4: Debating. BNB Chain clears the floor on the research limb rather than the proposal limb: there is no post-quantum BEP, but the core team ran and published ML-DSA-44 testing against BNB Chain's own throughput and block size, which is a public research programme by people with authority over the protocol. It is not Tier 3 because BNB Chain has published no plan to adopt a post-quantum scheme, only the results of testing one.
source
3 NIST alignment 5/10, weighted 15%
Band 3 to 5: NIST schemes are referenced as candidates without a committed selection, or the work is bespoke research.
The testing used ML-DSA-44, a parameter set of the final FIPS 204 standard, which is a specific and sound selection.
source
Placement in the band The top of the band rather than a 3 or a 4: ML-DSA-44 is a specific parameter set of a final standard, which is a concrete and sound selection. It cannot reach 6 because a scheme used in a test is not a scheme the chain has committed to adopt.
4 Migration path 3/10, weighted 15%
Band 3 to 5: Migration is acknowledged as a problem with no agreed mechanism, or the mechanism is contested.
BNB Chain's validator set is comparatively concentrated, which in principle makes coordinating a protocol change faster than on a more diffuse network. Against that, no migration plan for existing holders was found, and the published performance results suggest a naive migration is not viable without aggregation work.
source
Placement in the band The floor of the band rather than a 4 or a 5: validator concentration would make coordination easier, but no migration plan for existing holders was found and BNB Chain's own benchmarks suggest a naive migration is not viable without aggregation work.
5 Exposure 2/10, weighted 10%
Band 0 to 2: Public keys are exposed for effectively all accounts, or a large, measured share of total supply sits in exposed addresses.
As an EVM chain, a BNB Chain address is a hash of the public key, so a funded account that has never sent a transaction keeps its key private. In practice nearly every account holding meaningful value has transacted and published its key.
source
Placement in the band At the top of the band rather than a 0 or a 1: the hashed-address model does protect never-signed accounts, unlike the account-model chains at the floor of this band, though high transaction volumes leave little of value covered.
6 Verification 2/10, weighted 5%
Band 0 to 2: No post-quantum component exists, or the claims rest on marketing.
No post-quantum component protects BNB Chain. Its ML-DSA-44 tests were real and the results were published, but the code is a proof of concept on a branch whose pull request was closed without merging, and it runs on no persistent network. Under v1.8 an unmerged proof of concept is not a component, and published measurements are not review of code.
source
Placement in the band The top of the band rather than a 0 or a 1: there is no post-quantum component to verify, but nothing about the chain is marketed as quantum-safe, so its position does not rest on marketing.