QoreChain Implements Complete NIST Post-Quantum Cryptography Stack on Public Mainnet quantumcomputingreport.com
A live mainnet tx with ML-DSA-87, ML-KEM-1024 and SHAKE-256, because apparently consensus needed more acronyms.
5 comments
Does putting ML-DSA-87 and ML-KEM-1024 on a live mainnet mean old wallets can still verify or talk to it somehow, or is this only for clients that already know the new PQC formats?
Old wallets cant sign or verify them, only upgraded clients can.
Seeing a full ML-DSA-87 and ML-KEM-1024 path on mainnet made me wonder what the tx size and fee hit looks like compared with the usual stack, since that part seems like the thing people will feel first?
If they really put ML-DSA-87 signatures and ML-KEM-1024 material on chain, the first pain point is usually size, since you are in kilobytes per tx instead of a few hundred bytes, so I would expect the fee impact to come more from calldata and state growth than from verification itself.
Size is probably the first wall, but I’d want to see the actual per-tx split, signature bytes vs KEM payload vs any extra pubkey encoding, since those are very different fee drivers on Cosmos/EVM paths.
What happens when they try to batch or aggregate anything here, do fees still scale linearly with each PQC element, or did they hit a baseline where verification was cheap but block propagation and mempool acceptance became the bottleneck?