BNB Chain's BSC Post-Quantum Cryptography Migration Report shows the network has tested a post-quantum upgrade using ML-DSA-44 for transaction signatures and pqSTARK for consensus vote aggregation. The core design passes, and existing addresses, RPCs, SDKs and wallets remain compatible.
Why it matters
The headline test is a real milestone for a top-tier L1 — most major chains are still on the roadmap for post-quantum migration, and BNB Chain is now reporting measured results rather than promises. Backward compatibility with the existing address and wallet stack matters: a hard cutover would have fragmented the ecosystem.
Market impact
The cost lands on the data layer. Signature size jumped from 65 bytes to 2,420 bytes — a roughly 37x increase — and cross-region TPS fell by about 40% under load. $BNB remains a throughput-sensitive chain for DEX and GameFi traffic, so a 40% throughput regression is not a free lunch. BNB Chain's own report flags network and data-layer scaling as the main blockers before production deployment, which means any production cutover will need either aggressive layer-2 offloading or signature aggregation work to claw the TPS back.
Frequently asked questions
-
What did BNB Chain actually test in the post-quantum upgrade?
BNB Chain tested ML-DSA-44 for transaction signatures and pqSTARK for consensus vote aggregation. The core design passed, and the report says existing addresses, RPCs, SDKs and wallets remain compatible.
-
Why did TPS drop about 40% after the upgrade?
Signature size rose from 65 bytes to 2,420 bytes — roughly 37x — adding heavy data overhead to every transaction and consensus vote. That overhead is what dragged cross-region TPS down by about 40% in testing.
-
Will the post-quantum upgrade break existing BSC wallets?
No. BNB Chain's report says the design stays compatible with existing addresses, RPCs, SDKs and wallets, so users should not need to migrate funds or change tooling as a direct result of the cryptography switch.
-
Is the post-quantum upgrade live on BNB Chain mainnet?
Not yet. BNB Chain says the test results are out, but network and data-layer scaling remain the main blockers, so a production deployment is still in the engineering phase.
-
How could BNB Chain recover the lost TPS before mainnet?
Likely paths include pushing more transaction execution onto L2s, compressing or batching signatures, and signature-aggregation work — all of which move the per-transaction data cost off the consensus layer.
WuBlockchain