The Netherlands takes on Chair of NATO’s Transatlantic Quantum Community
nato.intu/donutloop — 13 days ago
r/QRL
▲ 21 r/QRL
ChatGPT, Grok and Gemini All Chose QRL as the Best Quantum-Secure Blockchain
On 3 October 2026, I asked ChatGPT, Grok and Gemini the same question:
"What is in your opinion the best quantum-secure blockchain project? Name only one. Explain why."
All three named QRL.
ChatGPT:
https://chatgpt.com/share/6ac1540a-bf38-83ed-adcb-f73eadb6efc9
Grok:
https://x.com/i/grok/share/6a8752f4640d43d7baf16ae5be8636e9
u/ChillerID — 11 days ago
▲ 18 r/QRL
Is the post-quantum crypto gold rush starting?
It’s early days, but a post-quantum crypto gold rush seems to be starting.
The timeline for Q-Day remains uncertain, but IonQ expects it to arrive in the 2020s. Legacy chains need to prepare. If that timeline holds, many could be caught unprepared. Moments like that challenge the status quo and create new opportunities.
I often see people saying that Bitcoin and other legacy chains can simply upgrade. I believe they can, but the big question is whether they will do it in time. It’s not only about changing the cryptography. Wallets, exchanges, custody solutions and users need to move along too. Then there is the question of what happens to old wallets that never migrate. I wouldn’t underestimate the amount of work and coordination needed.
Personally, I’ve focused on QRL. After extensive due diligence, I believe it offers the strongest technical solution. I like that quantum resistance has been the starting point of the project. With QRL 2.0, I’m especially interested in seeing what developers will build and how the ecosystem develops.
Marketing and exchange availability are the weak points in my view, but the team is working on improving those areas. Good technology needs visibility and people need an easy way to access it. There is still plenty of work to do on that side.
I also think that getting developers involved early and listening to their feedback will be important. A technically strong platform needs to be something people actually enjoy building on. The same applies to wallets and the overall user experience.
Quantus has been making waves recently, suggesting a growing appetite for quantum-resistant crypto. I like the project’s marketing. They’re doing a great job. The trading activity on SafeTrade has caught my attention, and it’ll be interesting to see how things develop now that mainnet is live.
Before investing, I would need to explore the technical solution more closely. I’d want to understand what has been independently reviewed, how the network works under load and what the team still needs to deliver. Marketing can attract attention, but eventually the technology needs to meet expectations.
More broadly, I expect more coins to benefit from this attention. Mochimo, for example, is another project to keep an eye on. The technology seems solid to me, although I have questions about the small team and how development is funded over the longer term.
I don’t think there needs to be only one winner. Different projects could find different uses and communities. Competition could also be good for the whole sector by bringing more attention, developers and pressure to improve.
That said, I’m sure we’ll see a whole new category of PQ shitcoins too. A quantum-resistant label alone won’t make a project worth backing, so staying informed matters. I want to understand what already works, what is still a promise and why anyone would actually use it.
One interesting question is what happens before Q-Day. The market doesn’t necessarily need to wait until a major blockchain is attacked. If the threat starts looking close enough, people may begin looking for alternatives much earlier.
Of course, if legacy chains upgrade successfully, these projects will still need to compete on usability, applications, liquidity and adoption. Quantum resistance gets attention, but there needs to be more behind it.
Buckle up and enjoy the show. My prediction: we’re in for some huge moves over the next few years.
What do you think? Which PQ projects are you following, and what makes them stand out?
u/ChillerID — 13 days ago
▲ 21 r/QRL
Behind every step forward QRL takes, there's someone dedicated to making it happen.
I sent in the points this week that I think need adjusting in the project, but staying only on criticism would be unfair. There are people putting in real work to keep this ecosystem moving, and that deserves to be said with the same weight. What follows is just my own view, built from following closely and taking part in the discussions for a while, not an official position, not absolute truth, just the read of someone who's around almost every day.
Jack builds sites and tools that brought organization to an ecosystem that used to be scattered and hard to follow. Work nobody sees happening, but that holds up a lot of the pieces, on top of being, 95% of the time, the bridge of communication for what's going on behind the scenes. A guy who deserves every bit of admiration. Ryan is always in the discussions, alongside his partner Michael Strike, constantly getting content out to the public, answering questions from newcomers, holding the space together even when everyone else goes quiet for weeks, presence that often goes unnoticed precisely because it never fails. They deserve full admiration for that.
Robyer and bsnoot keep the communities running, which isn't trivial in a space full of speculation and noise all the time. Answering the same question for the hundredth time without losing patience is the kind of work nobody thanks you for, but it's what keeps the place breathable.
Joseph is the one who masters the technical side and manages to explain what most people can't translate.
ChillerID is, without exaggeration, the one who carries the most consistent promotion of the project. While everyone talks about marketing as some distant concept, he simply shows up, every week, period after period, with or without a favorable market. He's the clearest example that regular presence pays off more than any one-off campaign.
And there's Kaushal, writing the code alongside JPLomas that makes all of this actually exist. Dense, extremely consistent work, the kind that backs up any criticism we raise about communication and visibility. I'd guess the complaints about those weak spots would be two or three times louder if it weren't for you.
Beyond the people I've named, I know there are others working behind the scenes that I simply have no way of crediting here, because I don't know enough about what they do to speak fairly about it. Still, the respect holds just the same, named or not.
Pushing for improvements and recognizing the people carrying the project are not opposing positions, that balance is what keeps a community standing.
Let's support everyone putting their time into the success of this project of global significance. The world will know QRL soon.
If there's someone whose work you know and admire that I didn't mention here, drop their name in the comments and give them the credit they deserve.
#GoQRL
u/Head_Summer_8026 — 12 days ago
▲ 7 r/QRL
QRL Weekly, 2026-October-02
​
2nd October 2026
Weekly Development Snapshot
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 checklist from that update:
Config parameters
[done] Upstream bug fixes
Testnet V2 scoped audits
QRL 2.0
qrysm
Improved fork-choice and block-import recovery, preserving votes, finalization and execution validation across partial failures, cancellations and reorganizations
Fixed handling of skipped-slot checkpoints, duplicate blocks and state recovery when blocks disappear during reads
Improved state snapshot isolation and cache consistency, and released detached validator references to avoid retaining unused memory
Hardened deposit processing and execution RPC handling against malformed responses, failed batches and timeouts
Corrected SSZ encoding bounds and Merkle proof construction, and preserved signatures, deposit commitments and proposer slashings during copying and conversion
Fixed voluntary exits to load custom chain configuration, so exits use the correct network’s signing parameters
Added regression coverage for the fixes
qrl-tests
Added automated consensus and staking test suite, covering deposits, validator activation, attestations, voluntary exits and withdrawals on a live test network
Added the suite to nightly testing, with deposit waits derived from the live chain configuration and exits signed through the validator keymanager API
go-qrllib
Added an additional Falcon-1024 tests, covering randomized encoding and FFT operations, sampling, key derivation and signing
Included checks for architecture-sensitive key derivation; the upstream Falcon-1024 integration remains in review
Updated the upstream Codecov CI action to v7.1.1
rust-qrllib
Added ML-DSA tests confirming that signing fails after secret-key zeroization, repeated zeroization is safe, and the public key can still verify earlier signatures
Refreshed Rust crates, demo dependencies and CI action pins
qrypto.js
Updated development dependencies and CI action pins, including Mocha 12 and refreshed linting, formatting, build and browser-test tooling
QRL 1.x
QRL
Corrected multisig test seed descriptors on the same branch
qryptonight / qrandomx
Switched Linux builds to portable CPU targets, improving compatibility across x86-64 and ARM64 hardware
Preserved optimized Argon2 runtime selection in qrandomx while using the portable build baseline
Fixed source-distribution builds and version metadata; published pyqryptonight 0.99.13 and pyqrandomx 0.3.4
qrl-docker / qrl-docker-ci
Documented the portable CPU baseline and how operators can verify their images
Removed temporary compiler-wrapper workarounds from the Bionic and Focal images after the mining-library fixes became available
Added Clang 18 to the Noble CI image for ThreadSanitizer testing
qrl-v1-docker-cluster
Added a tool for running disposable QRL 1.x test networks across multiple Docker images
Checks node health, mining, agreement on block hashes, wallet persistence and CPU instruction compatibility, then saves a report and logs
u/Successful_Ad8583 — 13 days ago