Bounty increased! (Aug 14, 2026)

The ECDSA.fail challenge has now reached 50.5% ahead of Google’s estimated quantum capability.

The target is 52%, meaning just 1.5% remains.

500 QRL to the first competitor who reaches 52% ahead of Google's estimated quantum capability in the ECDSA.fail challenge.

Good luck to all participants!

How to claim the bounty:

• Add your X account to your GitHub profile linked from the ECDSA.fail leaderboard.
• The first participant to reach 52% on the ECDSA.fail leaderboard will be contacted directly via X from my (ChillerID) account.
• If you don't already have one, create a QRL wallet and reply with your wallet address once contacted.
• After verification, the 325 QRL bounty will be transferred to your wallet.

Eligibility:

• If the first participant to reach the threshold cannot be contacted or does not respond within 5 days, the bounty will be awarded to the next eligible participant on the leaderboard.
• A reachable X account linked from your GitHub profile is required.

Note: This is an independently organized, QRL community-funded bounty and is not affiliated with, endorsed by, or administered by the QRL Foundation or Eigen Labs.

https://preview.redd.it/gx9yu7op2bjh1.png?width=1535&format=png&auto=webp&s=f926dac96d7a64fe18965d31ec826abb49fd53b3

What is different about solo staking versus joining a staking pool? If someone were able to put together 40,000 QRL to run a solo node would there be any unique benefits?

Is there anybody on the fence about the decision in this community? I'd be curious to hear your perspective.

The Quantum Readiness Index currently gives QRL a score of 100, ranking it #1 among the projects assessed.

QRL was built around post-quantum security from the beginning, rather than trying to retrofit quantum resistance onto an existing architecture.

As awareness of the quantum threat grows, it will be interesting to see how quickly the rest of the blockchain industry can close the gap.

Explore the methodology, criteria and full rankings at qrindex.org.

https://preview.redd.it/vmkvfaubweih1.png?width=1536&format=png&auto=webp&s=bd66b31378ba075418c8d87f4bac5736c16b6be1

I've mostly seen quantum computing discussed as a threat to crypto, but there's another side to it that I find interesting.

If quantum technology eventually becomes practical, it could potentially improve things like optimization, simulations, cryptography research, and other areas that could benefit the broader blockchain ecosystem. Faster or more sophisticated computation could even create new possibilities we haven't considered yet.

The obvious problem is that the same technological breakthrough could also challenge some of the cryptography that today's blockchains depend on.

So I'm wondering where people stand on this. Should crypto see quantum computing primarily as a threat that needs to be defended against, or as an opportunity where the industry should start adapting early?

And are there any projects actually experimenting with quantum-resistant infrastructure in a meaningful way, rather than just adding it to their roadmap?

Status / overview

• 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: 50% completion

QRL 2.0 (Project Zond)

qrl-web3-wallet

• further security-audit remediation and code-review fixes
• corrected address display and updated documentation

web3.js

• updated CI actions and patched vulnerabilities affecting fast-uri, PostCSS, SVGO and brace-expansion

js-qrl-cryptography

• updated pinned GitHub Actions and the fast-uri dependency

go-qrllib

• updated pinned GitHub Actions and opened further test-related work

qrypto.js

• updated development dependencies, lockfiles and CI actions for mldsa87

qrvmc

• Harden hex parsing, example VMs, and loader
• Tighten gas validation, loader TLS and ABI docs

go-qrl

• –bootnodes flag now override config value
• Go toolchain updated to 1.26.5
• external function values updated to 64-byte address plus a 4-byte selector
• Removed legacy local testnet script (now being moved to new repo qrl-tests)
• Several other bug fixes

qrysm

• Updated tests
• Go toolchain updated to 1.26.5
• Updated QRL dependencies
• Update the staking deposit CLI default to the valid deposit contract address
• Default address aligned with the Qrysm network config
• Fix Zond consensus version descriptor

web3.js

• ICAP and IBAN support removed as those are deprecated
• Added 64 byte topics and 512-bit integers data type

qrl-package

• Changes merged related to 64-byte address

QRL 1.0

dice

• 2018 Python script rewritten as JavaScript application
• session isolation, CI and browser end-to-end tests
• a verifiable single-file offline release

qrllib

• added RNG-regression protection
• modernised Emscripten support
• migrated release processes to GitHub Actions
• added trusted publishing and npm/PyPI deployment
• v1.2.6 released

offline-wallet-generator

• merge of v3 wallet format with stronger encryption and password security
• added reproducible offline builds, CSP tests and a security-focused CI/release pipeline

qrl-wallet

• 7 issues closed
• continued UI refinements
• gated multisig signing on validation and tighter OTS-reuse checks
• applied security hardening and documentation updates
• v1.9.1-beta in pre-release

qrllib-browserify

• updated support to Node.js 22+
• rebuilt the bundle for qrllib 1.2.6 and corrected module export and Browserify interoperability

qrl-cli

• replaced the aes256 dependency with scrypt-derived AES-256-GCM encryption while retaining compatibility with legacy wallet files