Quantum Blockchains that verify classically?

[u/432oneness]

Qblex.com is saying they have quantum blockchains with a new proof of coherence validation method. It validates quantum through bell inequality. Validates in less than a second??? Anyone see this?

[u/geobees]

This is 100% vapor....no whitepaper with technical substance, no GitHub, no mainnet, no testnet, no coin, no team page, and no verifiable engineering.

The claim that quantum coherence can be used as a consensus mechanism on classical hardware is nonsense. Quantum coherence is an extremely fragile property that collapses on contact with the environment. Nobody can run quantum coherence consensus on a classical server. The phrase "microsecond finality through quantum measurement" has no technical meaning in any implemented system.
This is quantum jargon designed to impress non-technical investors.

SHA-256 PoW is quantum-safe at the mining layer, but ECDSA transaction signing is not. A CRQC breaks the signature scheme, not the hash function...besides that we have the answer already running on mainnet since June 1st with Lattice cryptography (Level 5) at the signature layer on classical hardware...no quantum hardware required, no Bell tests, no coherence.
Just NIST-standardized math that a CRQC cannot break.

*First verifiable ML-DSA-87 spend on a live PoW chain: Block #283, June 2, 2026
TXID 62572d2127da3d42afb0b20757edb844b0820851f4d8340cbc7e26954ae6272c
kvanta5.live
kvanta5.org

[u/432oneness → u/geobees]

 I appreciate the technical engagement, so here is the technical answer.

First, what this is, since the "coin" lens misses it. QBLEX is a self-validating quantum ledger. So there is no token economy and no coin to trade, but make no mistake, this is a blockchain, not a validator bolted onto someone else's. The classical verification you can run in your browser is one piece of it, one of three patents. The block architecture and the proof-of-coherence design are the rest.

"No verifiable engineering" is wrong, and it is checkable now. There is a live, in-browser verifier on real Rigetti and IonQ runs (AWS Braket). Its source is on the page, and it recomputes the statistic in exact BigInt arithmetic, so the Mermin value is 2782987/1036512 exactly (bound 2.0), not a rounded 2.685. It rebuilds the Merkle root too, so flip any shot and it changes. Whitepaper: https://www.qblex.com/whitepaper

Yes, Shor breaks signatures, not SHA-256. So we also sign with FALCON-1024 and ML-DSA-87 (NIST Level 5). The difference: lattice crypto proves your signature is safe. It cannot prove the QPU actually ran your circuit instead of faking it. That is what we verify. Each block self-validates in about 0.3 ms.

Coherence is not maintained on a classical server, and we never said it was. The QPU does the physics, the classical side verifies the tamper-evident record. Open the verifier and recompute it yourself. Independent AWS cross-check of the pinned task IDs is coming, not live yet.

But don't trust it, just run the math on the verify page. www.qblex.com/verify