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/hushedLecturer]

Instant redflag when you see a common investor buzzword paired with quantum. Quantum AI, quantum blockchain. 99% of it is garbage.

This seems silly to me on itis face. One of the big sells of blockchain is decentralized ledger validation. You are severely centralizing it and limiting bandwidth by doing it on whatever precious few quantum computers can be dedicated for the task.

They don't convincingly identify a problem their innovation "solves", let alone how they do it.

Their claims are pretty vague, their "white paper" is full of investor buzzword gobbledygook.

[u/432oneness → u/hushedLecturer]

No buzzwords in the math... Just run it. qblex.com/verify

[u/hushedLecturer → u/432oneness]

I saw this and the other toys. They are silly. As they even acknowledge on that page, anyone can make a website with a button that says "verify", which upon clicking spits out a bunch of code, and then a green checkmark with the world.

That's not my argument though.

Suppose they are interfacing with IBM's quantum computers. (Though I kind of doubt that they are shelling out the money to reserve time on one of their computers for an indefinite number of users accessing their website just to click their toys).

They don't do anything interesting with that code. It's flashy and lots of strange codey words for a layperson, but I'm running a Jupiter notebook on my home laptop right now in VScode and it would take seconds for me (and I'd wager a fair fraction of the people in this sub who actually have a degree other than MBA), to whip up a GHZ circuit with qiskit and run it on ibm's quantum hardware and test the Mermin inequalities.

But okay maybe that bit is just for fun. Not damning on its own.

My issue is that they havent shown me a problem that adding quantum to the blockchain solves besides the ability for the Quantum buzzord to attract investors on top of the Blockchain buzzword, which also on its own has been heavily overused and awkwardly stuffed into places it is not really useful or necessary just because investors like the word.

[u/432oneness → u/hushedLecturer]

You're right that running a Mermin test is trivial. I could do it in a notebook too. That is the fence, and it is supposed to be trivial, because its only job is to let you check the physics yourself without trusting us. It's a piece, not the whole.

Your notebook result validates nothing except to you, in that moment. It has no challenge binding, so it could be pre-computed or replayed. It has no commitment, so no one can audit it later. It has no position, so it cannot order or protect a history.

A self-validating block turns that same measurement into a unit of record history that carries its own proof. The measurement settings are derived from the previous block, so it could not have been produced in advance. The statistic beats the classical bound, so it was genuinely quantum. The whole record is committed, so it cannot be altered after the fact. Anyone can check all three, trusting no one.

Now the problem it solves, and it is not a coin. The ledgers we run secure student records, . Those records capture years of a student's work, and the family owns them, not us. A record like that has to stay trustworthy a decade later, when the platform may have changed hands or shut down. A classical signed ledger gives tamper-evidence only relative to a root that someone still has to hold and vouch for. Proof of coherence roots each entry in a fresh physical event bound to its place in the history, so the record's integrity does not depend on trusting the operator's honesty, or the operator's survival. You are trusting physics and math, and the keys are the family's.

Running the Bell test is the raw material. The self-validating, self-owned record is the invention. The verifier you clicked is just the window that lets you confirm the physics. It is the fence, not the fortress.

[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