r/QRL • • 1d ago

Discussion Crypto is selling off. So why is $QRL back above $1?

16 Upvotes

Quantum computers and AI have advanced to the point where they are likely to crack legacy crypto sooner than expected. Q-Day is now closer than ever. This could partly explain the recent sell-off.

About a week ago, well-known crypto author Justin Drake said that a paper describing a significant breakthrough in quantum computing would be published in November 2026. He compared it to Google’s famous March 2026 paper. Meanwhile, quantum companies such as IonQ are aiming to launch cryptographically relevant quantum computers (CRQCs) soon.

Crypto is running out of time. It’s unclear whether legacy crypto will upgrade in time. A migration that requires millions of users to take action is likely to take more time than we have, putting valuations under pressure.

I’ve followed this space closely for the past year and a half. I’ve learnt that the Quantum Resistant Ledger saw the risk coming early and has been natively quantum-resistant since 2018. It is one of the few projects built to withstand the threat that future quantum computers could crack elliptic-curve cryptography.

Three reasons I’m paying attention to QRL right now:

  1. QRL 1.x (PoW) protects digital assets using XMSS hash-based signatures. No stress about Q-Day.

  2. Audits and remediation for QRL 2.0 (PoS) are 70% complete. After launch, its mainnet will support smart contracts with ML-DSA-87, which offers the highest security level in the ML-DSA signature standard.

  3. A new exchange listing agreement has been signed, with the listing planned for after the QRL 2.0 mainnet launch. Negotiations for a Tier 1 listing are at an advanced stage.

The future of crypto is quantum-resistant. Preparing for that shift today could be the next asymmetric opportunity.


r/QRL • • 2d ago

Discussion QRL 2.0 Could Shape Crypto’s Future. Why Are So Few Trying?

24 Upvotes

For seven weeks I watched the same number. From September 18 to October 30, QRL's weekly update put audits at 60%. Every Friday I opened it hoping the number had moved. Every Friday it hadn't, and my doubts grew.

Then on November 6 it moved to 65%. On November 13 it reached 70%.

It reminded me of something a developer from a rival project once told me. Nobody else will attempt a full quantum-safe smart contract platform for a long time, they said, because it's too hard. I wasn't sure I believed it. So I looked at what it actually takes.

Protecting a wallet is the easy part: you swap one signature for another. A smart contract platform is a different animal. Thousands of validators sign votes around the clock, with signatures many times bigger than Ethereum's. You need a new compiler, new wallets and hardware wallet support. And every layer has to be audited, because one bug at the bottom breaks everything above it. Ethereum, with all its money and talent, is aiming for about 2029. QRL's small team is already working toward its third testnet.

So why take on something that hard? Look at what happened last time. Ethereum launched in 2015 and gave people something to build. By 2017, token sales had raised over $5 billion. The apps brought the crowd. Now imagine the morning a quantum computer breaks its first real key. Apps everywhere will need a safe place to run, and QRL 2.0 wants to be that place.

And it might not stop with 2.0. QRL 2.0 is a hard fork: a new chain with new rules, and the move to it is happening either way. But a hard fork doesn't have to switch off the old chain. The old chain keeps running for as long as people run its software. So once 2.0 is up and running, QRL 1.0 could keep going alongside it. Ethereum didn't replace Bitcoin, and the two kept growing side by side. It's only an idea, but if 1.0 does keep going, a busy QRL 2.0 could bring new attention to it the same way.

So how far along is QRL 2.0? The team is building from the bottom up, and you can follow the audits layer by layer.

First, the cryptography: the code that creates keys and signs and checks every transaction. Trail of Bits audited go-qrllib, the Go library the node runs on. Halborn audited qrypto.js, the JavaScript library that wallets and apps use. Every finding was resolved, and both reports are public.

Next, the tools. The Ledger app finished its audit and fixes in September, and the tool that verifies official releases finished its audit too.

Then Hyperion, the language developers will write smart contracts in. Ciphsure audited it, and the fixes shipped this week in Hyperion 0.3.1. That's part of why the number finally moved.

That leaves the two programs that run the chain itself. go-qrl runs transactions and contracts. qrysm runs proof of stake, where validators agree on which blocks are real. Their audits are what's left, and the weekly update puts that internal audit work at 85%. Both are built on Ethereum's software, code that has been battle-tested on Ethereum for years, including some tough moments that Ethereum's developers fixed. The hard part is what QRL changed: it swapped in quantum-safe signatures, and that part is brand new.

QRL 2.0 is clearly making progress, and the team has come a long way. I can't say when it will be finished, or whether there will be more delays. What I can say is that the number is moving again, and that's good to see. I wish the team the best on the way to the finish line.

Originally posted on QRL Hub. QRL Hub is independent and not associated with the QRL Foundation. This is for information only and is not investment advice.


r/QRL • • 2d ago

Quantum News QRL Weekly, 2026-November-13 Status

12 Upvotes

QRL Weekly, 2026-November-13 Status

  • September 18th: QRL Release Verifier audit complete

  • September 11th: Ledger app audit and remediation complete

  • August 4th: Audit results published for go-qrllib

  • April 3rd: Audit complete of 2 cryptographic libraries

  • March 31st: QRL 2.0 Testnet V2 released

  • Audits & Remediation: 70%

QRL 2.0 Testnet V3 remaining checklist

  • [80%] Config parameters

  • [85%] Testnet V2 scoped internal audits (goqrl, qrysm remaining)

  • [60%] QRL v1.0 -> v2.0 migration testing

  • Note: No ETA, but watch this space, things are getting close.

QRL v2.0 Hyperion

  • Multiple audit/fix PRs + Hyperion 0.3.1 released

  • Continued compiler audit remediation: parser/nesting robustness, struct getters and array clearing, storage-slot width constrained below 2^256, plus substantial compiler correctness work.

QRVMone

  • Major VM/state-test alignment: storage keys constrained to 32 bytes like go-qrl

  • normalised storage-key JSON decoding

  • CREATE2/trie/transaction encoding aligned with go-qrl

  • runner added

  • t8n allocation (transition allocation) handling corrected and docs substantially rewritten.

  • Released QRVMone 0.13.0.

hypc-js

  • Significant runtime/CLI hardening, including restricted import directories, safer callbacks/SMT handling, compiler recovery and linker work.

  • Updated to Hyperion v0.3.1, followed by an npm-publish fix.

hypc-bin

  • Hyperion v0.3.1 binary release merged

  • Added the Hyperion 0.3.1 compiler binary and release metadata, completing the compiler release chain across Hyperion, hypc-bin and hypc-js.

ledger-app-qrl-v2

  • Updated dependencies/CI, corrected the P2 range for requesting signature chunks, adjusted coverage behaviour and prevented incompatible pycryptodome 4.x Dependabot upgrades.

qrypto.js

  • Consolidated dependency maintenance, updated globals/Rollup and related tooling, tidied minimatch handling and updated Zizmor CI tooling.

wallet.js

  • Dependency and CI maintenance plus an .mjs build asset and Zizmor/tooling updates.

js-qrl-cryptography

  • Consolidated dependency/CI updates and pinned monocart-coverage-reports for compatibility with c8.

qrlft

  • Updated the go-qrllib dependency used by the file-signing tooling.

rust-qrllib

  • Applied pending Rust/demo dependency and CI-action updates.

QRL v1.0 QRL node

  • Security backport merged

  • Hardening for the wallet API and OTS queries into QRL v1.

Ledger-QRL-JS

  • Added device-free and Speculos emulator tests, CI and dependency updates, substantially improving Ledger integration testing without requiring physical hardware.

block-explorer

  • Upgraded to Meteor 3.6 and Node 26, added Playwright smoke tests and Actions linting, pinned the Playwright image, fixed smoke CI and Windows bundle preparation, and updated dependencies.

qrl-cli

  • Dependency consolidation covering moment, u/grpc/grpc-js, brace-expansion, handlebars, fast-uri and undici.

webtools

  • Tightened the Node engine range, updated the ML-DSA signing-action pin, and refreshed Vue/Tailwind/Vite and CI dependencies.

qrl-wallet

  • Electron / undici / fast-uri maintenance.

offline-wallet-generator

  • Dependency and CI maintenance, including grouped dev-dependency and Zizmor updates.

api.theqrl.org

  • Updated dependencies and README documentation.

dice

  • Development dependency fixes including serialize-javascript and fast-uri.


r/QRL • • 3d ago

Discussion How was I able to download the QRL app from the App Store if it’s delisted??

4 Upvotes

r/QRL • • 6d ago

Discussion My First Blog on QRL at qrlhub.com: Why QRL is my pick?

16 Upvotes

People ask me why I think QRL is the best quantum-resistant crypto when there are newer ones out there. My answer starts with something most people miss. Every blockchain uses cryptography in two places. Your wallet signs transactions to prove the coins are yours. And the network has to agree on which blocks are real, which is called consensus. Proof-of-work chains agree through mining, which only uses hashing. Proof-of-stake chains agree through validators who sign their votes. A coin is only as quantum-safe as the weaker of the two.

The kind of cryptography matters too. Elliptic curves, used by most of crypto today, will fall to a large quantum computer. Lattice schemes like ML-DSA are NIST's new standards, built to resist quantum attacks. Hash-based schemes rest on the fewest assumptions of all, only the hash functions every blockchain already depends on. And all of it should be open source and audited, so anyone can check.

CoinWalletConsensusOpen sourceAudits
QRL 1.0 (since 2018)XMSS, hash-based, 256-bit address hashProof of work, hash-basedYesRed4Sec, X41 D-Sec
QRL 2.0 (testnet)ML-DSA-87, lattice, NIST's highest level (about 256-bit). SPHINCS+ (hash-based) plannedProof of stake, ML-DSA-87, latticeYesTrail of Bits, Halborn, more under way
Mochimo (since 2018)WOTS+, hash-based, 160-bit address hashProof of stake since 2026, validator signing undocumentedSource-available, use restricted to MochimoOne external audit, auditor not named
Abelian (since 2022)Custom lattice schemeProof of work, hash-basedPublic code, no licenceNone found
Quantus (since 2026)ML-DSA-87 or ML-DSA-65, latticeProof of work, hash-basedYesNeodyme and Eiger completed, others in progress
Algorand (since 2019)Elliptic curve, Falcon opt-in since 2026Elliptic curveYesWidely reviewed
Ethereum (since 2015)Elliptic curveElliptic curve, hash-based planned for 2028 to 2029YesWidely reviewed
Bitcoin (since 2009)Elliptic curveProof of work, hash-basedYesWidely reviewed

QRL 1.0 is the only coin here that's hash-based in both places, and it has been that way for every account and every block since 2018, with nobody needing to opt in. Bitcoin shows why both layers matter: its mining is safe, but its wallets are exposed. Mochimo came closest, but its shorter address hash leaves a thinner margin. A quantum computer roughly halves a hash's strength, taking 256 bits down to about 128, but 160 bits to about 80.

QRL 2.0's real strength is crypto agility. Every 2.0 address starts with a small type tag that says which signature scheme it uses. ML-DSA-87 comes first, SPHINCS+ is planned next, and QRL's libraries already include Falcon too. New schemes can be added as cryptography evolves, without redesigning addresses or forcing everyone to start over. Combine that with proof of stake and smart contracts that are quantum-safe from launch, and you have a design built to last, not just to ship.

Is QRL perfect? No. 2.0 is still on testnet, audits are at 65%, and the team moves slower than I'd like. I'd also love to see the same agility extended to validator keys.

But QRL didn't add quantum resistance as a feature. It was built for it from the start, and built to keep adapting. That's why it's my pick.

Originally posted at: https://qrlhub.com/en/blog/why-qrl-is-the-best-quantum-resistant-coin


r/QRL • • 6d ago

Exchanges QRL Exchange Update

Thumbnail
theqrl.org
22 Upvotes

⚛️


r/QRL • • 7d ago

Quantum News Oak Ridge National Lab, IBM, and AMD Launch New Co-Design Platform for Quantum Error Correction

Thumbnail
newsroom.ibm.com
9 Upvotes

r/QRL • • 10d ago

Quantum News QRL Weekly, 2026-November-06

10 Upvotes

Status

  • September 18th: QRL Release Verifier audit complete

  • September 11th: Ledger app audit and remediation complete

  • August 4th: Audit results published for go-qrllib

  • April 3rd: Audit complete of 2 cryptographic libraries

  • March 31st: QRL 2.0 Testnet V2 released

  • Audits & Remediation: 65%

QRL 2.0 Testnet V3 remaining checklist:

  • [80%] Config parameters

  • [80%] Testnet V2 scoped internal audits (goqrl, qrysm remaining)

  • [60%] QRL v1.0 -> v2.0 migration testing

  • Note: No ETA, but watch this space, things are getting close.

QRL 2.0 Hyperion

  • Fixed 512-bit integer aliases and word-sized operations, Panic(uint512) handling, CREATE/CREATE2 address derivation, full 64-byte log topics, unsigned u256 ABI zero-extension, legacy function pointers, call-option/value/balance widths, addmod/mulmod, storage/recursion/returndata bugs, and Yul stack-too-deep diagnostics with proper source locations.

  • Also hardened Emscripten builds, tracked hypc-js as a submodule, produced a universal macOS binary, strengthened regression/differential tests, and formalised review of upstream Solidity bug advisories.

hypc-js

  • Significant wrapper/runtime hardening: restricted CLI imports to allowed directories; hardened compiler recovery, remote loading, CLI and linker behaviour; validated callbacks before copying Standard JSON input; improved error handling for callback failures, SMT errors and oversized solver output; upgraded to ESLint 10, TypeScript 6 and Node 22; removed memorystream; and pinned attestation verification to the signing workflow.

web3.js

  • Landed the prior audit/remediation work upstream, including dependency/security clean-up and subscription timing fixes.

  • Release infrastructure gained a reattest mode for already-published versions, fixed SBOM output handling, and a breaking-change/version-bump trigger.

hypc-bin

  • Tightened compiler-binary provenance by pinning attestation verification to Hyperion's release workflow, documenting the required gh CLI version, and updating Zizmor CI tooling.

rust-qrllib

  • Applied pending dependency and CI-action updates, including cargo-deny, crates.io auth, Rust cache and Vite.

Latch

  • Added social/Open Graph metadata and aligned the QR-frame timing specification.

https://www.theqrl.org/weekly/2026-november-06/


r/QRL • • 10d ago

Discussion 26 Quantum Companies. Only ONE Needs a Breakthrough to Put Crypto at Risk.

Thumbnail
isitqday.com
12 Upvotes

Quantum computing roadmaps are getting interesting.

This website tracks roadmaps from 21 quantum computing companies. There are an additional 5 vendors with no published roadmaps bringing the total to 26.

AI is accelerating research and development across the board. Shor's algorithm has become the de facto benchmark for quantum computing. Whether intentional or not, every advance toward that benchmark is an advance toward breaking the cryptography securing today's crypto networks.

The public timelines are worth watching, but what's happening in the labs on hardware that isn't available to the public could be even more interesting.

26 vendors. Five modalities. All well funded. Only ONE needs a breakthrough.

Nobody knows when a cryptographically relevant quantum computer will arrive. But assuming we'll see every major breakthrough coming seems unlikely, especially given the pace of recent advancement.

This is exactly why quantum-resistance matters.


r/QRL • • 12d ago

Discussion The kingdom of Quantara

5 Upvotes

In the kingdom of Quantara, the people's treasure rested beneath the Crystal Seal, forged to withstand the storm the mages called the Great Breaking. Before the queen could declare it unbreakable, the elders summoned the House of a Thousand Seals, the most respected in the land, to examine it.

The guardian Cymbbar welcomed the auditors with honor. He opened the archives, handed over the keys, and offered lodging to each of them. In the first few days, everything seemed as it should be.

But the weeks went by, and everything moved a little slower than expected. A pending scroll. A rune "under review." A deadline that slipped to the next moon, and then to the one after. No one complained, because no one had proof of anything.

One afternoon, Cymbbar walked through the east wing of the House and saw a banner that was not Quantara's. It was the banner of Etheria, the rival kingdom. The scribes explained, proudly, that the House had inspected Etheria many, many times. It was the wing's oldest and most illustrious client.

Cymbbar smiled and thanked them for the explanation. But as he left, he noticed that the best scribes spent their days in that corridor.

Across the mountains, Etheria never rested. Travelers crossing the border told of forges burning day and night, of blacksmiths changing shifts without ever letting the fire die, and of new walls rising with every moon. Etheria was running, and Quantara was waiting.

That night, Cymbbar opened a new notebook. He wrote down every visit, every request, and every postponed deadline, with the date beside it, as every good guardian should.

When the council met, the elders asked if something was wrong.

"I accuse no one," he replied. "The House is wise, and I am only grateful. But I ask: can one who has served Etheria for so long examine its rival without placing a thumb on the scale? And who benefits from every moon that passes without a verdict on the Seal?"

The elders fell silent. They knew that every day of delay was a day the Seal went without proof that it held, and that those without proof live on rumors.

Cymbbar did not raise his voice or point a finger. He kept working, writing, and waiting. When the Audit was over, the people could read the entire notebook, lay the dates side by side, and judge for themselves.

"Whoever examines two rival kingdoms must prove the scales are fair. Meanwhile, Etheria builds, and Quantara waits. Trust, but verify."


r/QRL • • 13d ago

Trading This is the big one

8 Upvotes

I think this dip will be the last big one before we rocket higher to a new price regime. Trump will unwind global markets further but once we hit a bottom, QRL will rebound. Godspeed. 🚀🚀🚀


r/QRL • • 15d ago

Questions Can you buy QRL w cash in the QRL wallet through BANXA?

4 Upvotes

As the title suggests, I just noticed in the wallet it says “buy now through banxa with fiat”. Has anyone ever bought it this way? Why isn’t that promoted more if so? I would think that would be far more simple for most then exchanging whatever crypto and transferring to one of the exchanges in order to buy it.


r/QRL • • 15d ago

Discussion Why this token? What separates it from others? Every major crypto seems to be preparing for quantum

4 Upvotes

r/QRL • • 16d ago

Discussion QRL Foundation Intervention?

3 Upvotes

TL;DR: Someone with deep pockets has been buying QRL for ~3 weeks to stop the price from falling under $1.22. In the current weak crypto market, nobody has a clear profit reason to keep doing this. The only party with a strong reason to spend money just to hold the price up is the QRL Foundation itself.

---

For the past 3 weeks a persistent bid wall around $1.22 has been absorbing selling and keeping QRL from trading meaningfully below that level. On a thin market with very low volume, one buyer (or algorithmic bids) can easily control the price this way.

This is expensive. The buyer keeps paying $1.22 instead of waiting for cheaper coins lower, and is building inventory against the prevailing market direction. After the recent Binance hack the broader crypto market is weak, QRL is not acting as a safe haven, and the quantum story is still too distant to justify strong buying. Pure market makers or normal traders have little incentive to take this kind of directional risk for weeks.

The only realistic explanation is deliberate price support by a party that has a non-trading reason to prevent a drop - most obviously the QRL Foundation (or someone acting for it). They hold large reserves and have the strongest interest in avoiding a sharp decline in sentiment on a low-liquidity coin.

PS: Let’s keep this focused on the current order-book behavior. Comments about quantum computers eventually breaking crypto, or about 2.0 being “just around the corner,” don’t explain why someone is actively supporting the price right now. Those are multi-year narratives - they’re not relevant to this discussion.


r/QRL • • 17d ago

Discussion QRL Weekly, 2026-October-30

4 Upvotes

Status

September 18th: QRL Release Verifier audit complete

September 11th: Ledger app audit and remediation complete

August 4th: Audit results published for go-qrllib

April 3rd: Audit complete of 2 cryptographic libraries

March 31st: QRL 2.0 Testnet V2 released

Audits & Remediation: 60%

QRL 2.0 Testnet V3 remaining checklist:

[80%] Config parameters

[80%] Testnet V2 scoped internal audits (goqrl, qrysm remaining)

[50%] QRL v1.0 -> v2.0 migration testing

Note: No ETA, but watch this space, things are getting close.

QRL v2.0

Hyperion

Continued heavy compiler hardening following v0.2.0 / audit remediations

Fixed Yul KnowledgeBase variable versioning so reassignment cannot leave stale offsets

Corrected deletion of individual memory-byte elements; widened the bytecode regression corpus

Prevented PyPI contamination of release builds

Hardened release/tag verification

Improved current macOS toolchain support and Windows verifier testing;

Updated dependency tooling and documentation.

web3.js (active cyyber fork work)

Large multi-pass audit/remediation effort across subscriptions, event filters, transports, RPC validation, receipts, ABI/raw-transaction handling and package-install policy.

Added stricter response/nesting bounds, subscription buffering/delivery fixes, receipt/log identity checks and diagnostics

Hardened QRNS registry-address handling

Documented VM64 breaking changes

Added a pinned two-CPU execution testnet launcher.

Latch

Latch went public this week as the new QRL v2 offline-signing application.

The shared PWA/iOS/Android design supports offline wallet creation/import, reviewed transaction signing, QR/file transaction exchange, encrypted vault/wallet backups and offline-install/storage checks.

Team preview for internal testing at latch.theqrl.org

QRVMone

Updated the QRVMC submodule, moved to QRVMC byte types, rejected invalid/out-of-range revisions, updated changelog/release metadata and fixed the Hunter/CMake 4 compatibility gate.

This work also feeds directly into Hyperion’s compiler/test matrix.

QRVMC

Replaced problematic std::char_traits<uint8_t> aliases with explicit byte_traits and released QRVMC 3.0.0, providing the byte types consumed by QRVMone.

hypc-js

Hardened the JavaScript Hyperion distribution pipeline: added npm trusted publishing, required release tags to resolve to commits on main, refreshed GitHub Actions and vulnerable dependencies, and added CODEOWNERS.

hypc-bin

Added compiler-binary verification workflows and release tooling, upgraded CI actions including Zizmor/setup-node, and added CODEOWNERS.

go-QRL

Continued QRL 2 execution-client convergence: made genesis-era fields mandatory, converted WithdrawalsHash to a value, improved pending-block decoding and qrlclient behaviour, and switched API/GraphQL/statistics code to SyncProgress.Done for completion checks.

Qrysm

Updated the consensus-client build against the corresponding go-qrl required-fields work (go-qrl#288), keeping Qrysm aligned with execution-layer API changes.

QRL v1.0

Zeus-Proxy

Improved automatic reconnection to QRL nodes when upstream connections drop, improving proxy resilience for v1 node/API users.


r/QRL • • 17d ago

Questions how to buy QRL?

9 Upvotes

r/QRL • • 18d ago

Trading BREAKING: World's largest crypto exchange Binance hacked with over $5.6 billion stolen:

18 Upvotes

BREAKING: World's largest crypto exchange Binance hacked with over $5.6 billion stolen:

• $1.45 billion

$BTC

• $875 million

$ETH

• $234 million

$TRX

• $50 million

$XAUT

• $1.57 billion

$USDT

• $823 million

$USDC

• $75 million

$WBETH

• $88.5 million

$RLUSD

+ $447.5 million additional cryptocurrencies


r/QRL • • 19d ago

Quantum News Infleqtion deal with US Commerce Department aims to accelerate American leadership in quantum computing

Thumbnail
foxbusiness.com
8 Upvotes

r/QRL • • 20d ago

Quantum News Quantinuum Breaks Error-Correction World Record by 10x, Validating Its Leading Path to Fault-Tolerant Quantum Computing by 2029

Thumbnail ir.quantinuum.com
14 Upvotes

r/QRL • • 20d ago

Quantum News Why Xanadu’s CEO sees a quantum data centre as the next big win for Canada

Thumbnail
begiant.ca
4 Upvotes

r/QRL • • 21d ago

Questions MEXC Iceberg

5 Upvotes

QRL on MEXC appears to be artificially supported above 1.22 by a single buyer, against the prevailing market pressure. The buy order book above 1.22 seems to be algorithmically adjusted, consistently maintaining a combined volume of 2,827.42 QRL.

Am I right to assume that it may be time to sell? At the moment, this entity appears to be the only thing preventing QRL from falling. If its buying liquidity dries up, the price could collapse rapidly unless positive news changes market sentiment.

I believe I have observed a similar pattern with QRL in the past. The key question is how deep this entity's pockets are and how long it can sustain this level of support. The pattern has persisted for at least a week.

Does anyone have insights into what might be happening here? More importantly, is there a way to exploit this behavior to our advantage?


r/QRL • • 23d ago

Discussion Quantum coins apparently aren't welcome on CoinMarketCap.

Post image
13 Upvotes

r/QRL • • 24d ago

Quantum News QRL Weekly, 2026-October-23

12 Upvotes

Status

September 18th: QRL Release Verifier audit complete

September 11th: Ledger app audit and remediation complete

August 4th: Audit results published for go-qrllib

April 3rd: Audit complete of 2 cryptographic libraries

March 31st: QRL 2.0 Testnet V2 released

Audits & Remediation: 60%

QRL 2.0 Testnet V3 remaining checklist:

[80%] Config parameters

[75%] Testnet V2 scoped internal audits (goqrl, qrysm remaining)

[50%] QRL v1.0 -> v2.0 migration testing (added)

Note: No ETA, but watch this space, things are getting close.

QRL v2.0

hyperion

added ML-DSA-87 verification builtin/codegen, SHAKE256 builtin support

added alignment with go-qrl precompile outputs,

added real-signature verification in the test host

argument-order fixes across IR/codegen/SMT

EIP-55-style fixes for wide mapping keys and indexed addresses

64-byte topic handling

ARM64 builds

release/CI fixes

removal of older ABI-v1 support

hypc-bin

added the Hyperion v0.2.0 compiler binary and release metadata

hypc-js

updated the JavaScript compiler wrapper to Hyperion v0.2.0

go-qrl

added SHAKE256 precompile at 0x06 and the 64-byte ML-DSA-87 verification frame at 0x03

added legacy QRL migration with streaming genesis initialisation

fixed ABI panic-selector handling with Hyperion compatibility tests

regenerated tracer/fixture codecs

improved devp2p, logging and Catalyst behaviour

continued general client clean-up

qrysm

updated go-qrl/go-qrllib dependencies following the new crypto and VM interfaces

fixed CI and validator fixtures

removed redundant documentation and obsolete derived-keymanager code

removed the contract-deployment-block flag

repaired tests affected by the newer SSZ bounds checks.

rust-qrllib

v0.1.8 released

dependency maintenance following the previous week’s addition of Falcon-1024 and associated ACVP validation.

QRL v1.0 -> v2.0

QRL v1 archive

continued native QRL v1 node recovery work as part of the archive/rehearsal process. This follows the previous week’s 1.62-million-block rehearsal and exact-byte exporter/verification tooling.

QRL v1.0

qrl-wallet

wallet UX and policy hardening: enforced server policy for custom nodes and desktop networking, added a CSS loading spinner while opening wallets, and improved performance by rendering the large OTS-tracker grid only when its dialog is actually open.

qrllib

updated JavaScript test dependencies (brace-expansion and js-yaml). No major functional library change landed in this window.

webtools

completed the outstanding grouped development-dependency update from the previous week.


r/QRL • • 25d ago

Discussion Bitcoin solved the Byzantine Generals problem. Quantum just reopened it.

17 Upvotes

In 2009, Bitcoin answered an old puzzle. Generals surround a city, they can only communicate through messengers, and some of them may be traitors. Proof-of-work made lying expensive, and digital signatures made every message verifiable, because only General A could have sealed a message in A’s name. For a long time, the solution held, and the puzzle seemed closed.

It reopened because the traitor changed. The old traitor was a dishonest general who had to be outworked. The new one is a quantum computer running Shor’s algorithm, which can derive a private key from a public one. The machine is coming, and a traitor could sign in any general’s name, leaving the blockchain with no way to distinguish the forgery from the original.

The cryptographic fix exists, since quantum-resistant signatures are already known. The unsolved part is the council. Bitcoin has no commander, so the generals themselves must choose the new scheme, persuade millions of holders to move their coins, and decide what happens to the coins whose owners are gone for good. Some of the earliest coins are locked directly to public keys, with nobody left to move them. Freezing them breaks the promise that no one can touch your coins, while leaving them vulnerable allows the first quantum thief to take them. Every path requires trusting someone, and eliminating the need for that trust was the very reason the system was built.

That is the second Byzantine problem, and it is about agreement. The deadline is set by a laboratory, and the generals can only hope to finish arguing before it arrives.

QRL’s generals skipped the argument. Their signatures have been hash-based since the first block in 2018, so there was never a council to convene.