After 74 days of post-quantum blocks in production, QOR begins trading on MEXC today, August 20, 2026, at 13:00 UTC in the QOR/USDT pair, with withdrawals opening August 21. MEXC ran it through its Kickstarter programme, distributing 3,000,000 QOR to participants ahead of the open. Whether the token survives its first week is, as always, a separate question from whether the cryptography does.
The test that actually matters
The milestone isn't the listing. It's the transaction on July 2, 2026, hash 4E49D57F86FEC8851CDC34811B4C80FDB24F4C253ABE15D25C05B7A27F2B7F1F, signed end-to-end with the full NIST-standardized post-quantum stack: ML-DSA-87 (FIPS 204) for the signature, ML-KEM-1024 (FIPS 203) for key encapsulation, and SHAKE-256 (FIPS 202) for hashing. The signature is byte-compatible with any independent ML-DSA-87 verifier. You can pull it off explore.qore.network and run it through a stock library without trusting a single line of QoreChain's code. That is a meaningful property, and it is rare.
The team's own litmus test for "quantum-secure" is brutal in its simplicity: delete the post-quantum signature and see whether the chain still accepts the transaction. On most self-described hybrid designs, the answer is yes — the quantum-vulnerable scheme still gates every state transition, and the post-quantum field is decoration. On QoreChain's native lane, the answer is no. Without a valid ML-DSA-87 signature at NIST security level 5, a transaction doesn't validate, isn't gossiped, and never reaches a block. The classical co-signature is tooling glue, not security.
What the codebase actually admits
Apache-2.0 matters because pretending expires the moment a skeptic reads the repo. QoreChain ships three execution environments — EVM, CosmWasm, and SVM — against a single state layer and a single consensus layer. That's an architectural choice with real blast radius: forcing lattice signatures onto the EVM on day one would detonate every secp256k1 assumption in the existing toolchain. So the EVM lane still verifies classical signatures, deliberately, while post-quantum machinery is already live around it. Solidity contracts can call precompiles at 0x0A01 (ML-DSA verification) and 0x0A02 (key-status lookup), on-chain post-quantum key registration is operational, and a governance-controlled enforcement mode is moving each lane from optional to required in phases through 2026. The project's own QoreX wallet already signs in hybrid mode. The cryptography was never the bottleneck. Migrating a live chain without orphaning its users is.
What I'm watching from here
The honest threat model starts with the migration window, not the algorithm. A staged rollout with a long tail of optional verification is also a staged rollout where a downgrade attack or a misconfigured node can quietly keep accepting classical signatures past its expiry. I'd want to see the governance timetables, the slashing conditions for validators that bypass the enforcement mode, and what happens to funds locked in contracts that never migrate their key registration. The transaction hash is verifiable. The rollout still has to earn the same property one phase at a time.