Bitcoin Forum
July 16, 2026, 10:30:38 PM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [ANN] Quantum-Lattice (QL) - Post-Quantum Layer 1 Blockchain (ML-DSA-65) | Live  (Read 201 times)
AlthaafM (OP)
Newbie
*
Offline

Activity: 6
Merit: 0


View Profile
July 13, 2026, 06:59:27 PM
 #1

Quantum-Lattice (QL)
A Layer 1 blockchain signed entirely with ML-DSA-65 — the finalized NIST post-quantum standard (FIPS 204)

The Problem
Bitcoin, Ethereum, and nearly every major chain sign transactions using elliptic-curve cryptography (ECDSA) — secure against classical computers, but vulnerable to a sufficiently powerful quantum computer via Shor's algorithm. This isn't purely theoretical: adversaries can record public blockchain data today and decrypt it once quantum hardware catches up, a strategy known as "harvest now, decrypt later."

What Quantum-Lattice Does Differently
Every single transaction is signed using ML-DSA-65, standardized by NIST as FIPS 204 in 2024, built on lattice-based hardness assumptions believed secure against both classical and quantum attacks.

What's Live Right Now
  • A real, working Layer 1 node — proof-of-work mining, automatic difficulty retargeting
  • A non-custodial browser wallet — keys generated and signed entirely client-side via WASM, recoverable via 24-word BIP39 seed phrase
  • Mining clients for Linux and Windows, TLS-secured, rewards paid directly to your own wallet address
  • A public block explorer with live chain data
  • A "Security & Transparency" page with real, independently reproducible cryptographic test vectors
  • Full source code, open and Apache 2.0 licensed on GitHub

Honest Disclosure
This is currently a small node cluster operated by the development team — broader decentralization is the natural next step as real usage grows. It has not yet undergone independent third-party security audit, though it has had careful internal review with test vectors published openly for anyone to verify. We'd rather state this plainly than have anyone assume otherwise.

Developed by
Futuristic AI — an independent systems engineering lab based in Durban, South Africa, specializing in post-quantum cryptography and low-level systems engineering.

Links
Explorer: https://quantum-lattice.futuristicai.co.za
Wallet: https://qlwallet.futuristicai.co.za
Source: https://github.com/AlthaafM/Quantum-Lattice

Happy to answer any technical questions.

This is not investment advice. QL has no exchange listing at this time.
Sparks60
Newbie
*
Offline

Activity: 54
Merit: 0


View Profile
July 13, 2026, 09:00:12 PM
 #2

after mining some coins, i see there is 48 ql per block at time of this post show 1438 blocks X 48=69,024  and the total outstanding is 5,269,024    so my guess is there is a 5.2M premine? i dont see any info about this on website. can you shed some lite on this just for clarity?
Sparks60
Newbie
*
Offline

Activity: 54
Merit: 0


View Profile
July 14, 2026, 01:33:33 AM
 #3

A real, working Layer 1 node — proof-of-work mining, automatic difficulty retargeting
how is this calculated? if a big cpu farm comes onboard, mines gets a bag, and leaves ,at what point will the diff drop back down when they leave?
AlthaafM (OP)
Newbie
*
Offline

Activity: 6
Merit: 0


View Profile
July 14, 2026, 04:57:41 AM
 #4

Quote from: sparks60
after mining some coins, i see there is 48 ql per block at time of this post show 1438 blocks X 48=69,024  and the total outstanding is 5,269,024    so my guess is there is a 5.2M premine? i dont see any info about this on website. can you shed some lite on this just for clarity?

Good catch, and you're right to ask.

Yes, there's a genesis allocation of 5,200,000 QL, split across two project-controlled treasury wallets — used for ongoing development, infrastructure, and things like security review and exchange listing costs down the line.

The public explorer shows the aggregate figures directly — max supply, circulating supply, and how much remains mineable — so the full picture is genuinely there. The individual vault addresses aren't proactively displayed on the explorer's front page for operational reasons as the network grows, though that's something we may add to the site down the line.

Appreciate you asking directly rather than assuming the worst — exactly the kind of scrutiny a project should welcome.

Quote from: sparks60
A real, working Layer 1 node — proof-of-work mining, automatic difficulty retargeting
how is this calculated? if a big cpu farm comes onboard, mines gets a bag, and leaves ,at what point will the diff drop back down when they leave?

Fair question, and genuinely tested this exact scenario over launch weekend. Difficulty retargets every 10 blocks, comparing actual time taken against the 5-minute-per-block target — it can move in either direction, not just up.

Concretely, what actually happened here: difficulty climbed from 22 to 31 bits over a weekend as more hashpower joined, then walked back down over the following retarget cycles once hashpower dropped. Not instant — it takes a few 10-block windows to fully correct — but it does genuinely settle back down, not stay artificially high forever.

So to your scenario directly: a big farm joining would push difficulty up while they're active, and after they leave, it corrects back down over the next several retarget windows as block times naturally slow back toward target.
Sparks60
Newbie
*
Offline

Activity: 54
Merit: 0


View Profile
July 15, 2026, 12:53:21 PM
 #5

mining at 41 leading zero bit(s)...
no wounder i have not won any blocks in the last day, diff just to high
AlthaafM (OP)
Newbie
*
Offline

Activity: 6
Merit: 0


View Profile
July 15, 2026, 04:59:01 PM
 #6

Yeah, 41 bits is real — difficulty's climbed a lot since launch as more people have started mining. Same mechanism we saw self-correct over the first test weekend (22 up to 31, then back down when hashpower dropped), just now responding to sustained real growth rather than a short test.

Worth being upfront: at 41 bits, a single average machine's realistic odds on any given block are genuinely low right now — that's not a malfunction, just the honest math of proof-of-work with more competition. If total network hashpower ever drops, difficulty will retarget back down over the following cycles, same as before.

Not much to do about it besides more hashpower, unfortunately — that's just the nature of solo mining against a growing network. Good to see you keeping a close eye on this, though.
AlthaafM (OP)
Newbie
*
Offline

Activity: 6
Merit: 0


View Profile
Today at 08:51:42 AM
 #7

Quick update: mining clients now support multi-threading

Real feedback from someone running a high-core-count machine (a Threadripper) flagged that the mining client was only using a single CPU core, regardless of how many were actually available on the hardware. Genuine, valid limitation — now fixed.

Both the Linux and Windows mining clients automatically detect and use every available CPU core by default, with an optional argument to override the count if you'd rather limit it. Tested and confirmed working — batch sizes now scale correctly with thread count on real multi-core hardware.

Updated downloads are live on the explorer now, and the source is updated on GitHub.

Explorer: https://quantum-lattice.futuristicai.co.za
13y85t
Newbie
*
Offline

Activity: 64
Merit: 0


View Profile
Today at 10:18:21 AM
 #8

discord ? tg ? other ?
AlthaafM (OP)
Newbie
*
Offline

Activity: 6
Merit: 0


View Profile
Today at 11:42:09 AM
 #9

Good question, and honestly, not yet — nothing official beyond this thread and the socials linked on the explorer right now. Given people are starting to ask, it's genuinely time to set one up. Will follow up here once it's live.
AlthaafM (OP)
Newbie
*
Offline

Activity: 6
Merit: 0


View Profile
Today at 12:23:09 PM
 #10

Following up — it's live now:

Telegram: https://t.me/+QfarLtaccHM0NzFk

Feel free to join and ask anything there directly.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!