[ANN] Quantum-Lattice (QL) - Post-Quantum Layer 1 Blockchain (ML-DSA-65) | Live

[AlthaafM]

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]

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?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]

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.

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]

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

[AlthaafM]

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.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]

discord ? tg ? other ?

[AlthaafM]

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.Following up — it's live now:

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

Feel free to join and ask anything there directly.

[AlthaafM]

Update: first independent, externally-operated full node

Genuine milestone worth sharing — Quantum-Lattice now has its first real, external node operator running their own independent copy of the chain, verifying everything themselves rather than trusting our servers alone. This is actual decentralization in practice, not just something the architecture allows for in theory.

Also worth noting: real network hardening shipped recently — connection timeouts and additional stability improvements, part of keeping things solid as more people run real infrastructure against the network.

Want to run your own node? Here's the full setup:

Linux:

Code:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
sudo apt install -y clang libclang-dev cmake pkg-config libssl-dev
git clone https://github.com/AlthaafM/Quantum-Lattice.git
cd Quantum-Lattice
cargo build --release
./target/release/quantum-lattice_core

Windows:
Install Rust from rustup.rs, and Visual Studio Build Tools (with "Desktop development with C++" checked), then:

Code:

git clone https://github.com/AlthaafM/Quantum-Lattice.git
cd Quantum-Lattice
cargo build --release
.\target\release\quantum-lattice_core.exe

First build takes a while (compiling RocksDB from source). First run asks you to set two passwords, encrypting local vault key files — pick anything, unrelated to real chain data.

To actually sync with the real network as a full node, you'll need a starting chain snapshot — email support-ql@futuristicai.co.za and we'll send a secure link.Update: nodes now sync continuously, and real peer visibility added

Two real improvements shipped:

Continuous peer sync — previously, a node only checked for missed blocks once at startup. Now it re-checks automatically on an ongoing basis, so it recovers on its own after any brief network interruption, without needing a manual restart. Found and fixed a real bug in the process too — a connection attempt with no timeout could permanently freeze the sync loop if it ever hung, rather than failing cleanly and retrying.

Live peer visibility — the admin dashboard now shows genuine, real-time evidence of which peers have actually connected and exchanged data with a node, independent of its own configured peer list.

Both tested extensively across multiple independent machines before shipping, including a real external node syncing purely over the internet and recovering automatically from a deliberately simulated interruption.

README updated with details on running your own full node: https://github.com/AlthaafM/Quantum-Lattice

[AlthaafM]

Update: Quantum-Lattice mining pool is now live

Genuine, real news — solo mining has always paid the full reward, but real luck too, especially as more people have joined and difficulty has climbed. Pool mining changes that: contribute alongside others toward a shared effort, and get paid a proportional share every time the pool wins, based on your actual contributed work.

How it works

The pool submits real, full-difficulty solutions to the network under its own identity, exactly like a normal miner. Connected contributors work on the same template at a much easier, pool-set difficulty, submitting "shares" far more frequently than a solo block would ever land. When the pool genuinely wins, it signs and sends real, individual payments to every contributor, automatically, proportional to their share of the work.

Same download, same wallet, just a different command

Code:

Linux:
./miner --pool ql-pool.futuristicai.co.za:7999 YOUR_WALLET_ADDRESS

Windows:
.\miner.exe --pool ql-pool.futuristicai.co.za:7999 YOUR_WALLET_ADDRESS

Same miner client, same download page — the --pool flag and the pool's address are the only difference from solo mining.

Tested before announcing

Before saying anything publicly, we ran two independent machines contributing real shares, funded the pool with real QL, and confirmed the actual payout split landed correctly in both wallets, proportional to each machine's real contribution — not just designed to work, actually watched working.

Per-contributor adaptive difficulty (so a high-end machine and a modest one both get an equally steady rhythm) is a real item on the roadmap, building on this initial version.

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

Happy to answer anything technical about how it's built.

[AlthaafM]

Update: mining pool upgraded with a full live dashboard

Real, substantial progress since the pool launched — here's what's new:

A live Mining Pool Dashboard — https://ql-pool.futuristicai.co.za

See the current round in real time: block height, real network difficulty, pool difficulty, active contributors, and combined pool hashrate — all genuinely live, refreshing automatically.

Live standings — a real-time leaderboard showing every contributor's share count and estimated hashrate, so you can watch your own contribution as it happens.

Permanent all-time stats — total blocks the pool has ever found, and total QL distributed to contributors, tracked permanently, not just recent history.

Main explorer upgraded too — click any block to see its full detail, including every individual transaction's sender, receiver, and amount. Search any block by number and jump straight to it.

Everything's connected — a direct link to the pool dashboard now sits right on the main explorer, next to the project overview.

This is what active, real development looks like — shipping real features fast, based on real community feedback. More coming.

Explorer: https://quantum-lattice.futuristicai.co.za
Pool: https://ql-pool.futuristicai.co.za
Source: https://github.com/AlthaafM/Quantum-Lattice

[AlthaafM]

Update: Quantum-Lattice Desktop Wallet is here

Real, substantial progress — a genuine, installable desktop application, built and tested on real hardware before announcing it. Same non-custodial, post-quantum security (ML-DSA-65) as the browser wallet — the actual proven signing code, just wrapped in a real native app instead of a browser tab.

Download for Windows — available now from the Wallet tab: https://quantum-lattice.futuristicai.co.za

Mac and Android builds are genuinely on the roadmap, not built yet.

Mining pool transparency upgrade

The pool dashboard now honestly separates two different things that used to be blended together:
- Genuine network wins — the pool actually finding a real block
- Manually-initiated bonus rewards — extra reward rounds contributors receive from time to time, on top of real wins

Both are tracked and shown separately, permanently, so nothing gets overstated.

Real, growing participation

The pool now has genuine, serious hashpower behind it, real contributors joining daily — a real, live leaderboard on the dashboard shows exactly who's contributing and how much.

Explorer: https://quantum-lattice.futuristicai.co.za
Pool: https://ql-pool.futuristicai.co.za
Source: https://github.com/AlthaafM/Quantum-Lattice

Happy to answer anything technical.

[fibonacciopstan]

Publishing independently reproducible test vectors is a strong step, especially for a project whose main claim is cryptographic security rather than marketing.

What may become difficult to verify later is the history surrounding those tests. Today, Quantum-Lattice openly states that the network is operated by a small development-controlled cluster, has not completed an external audit, and uses specific ML-DSA-65, wallet, mining and key-recovery implementations.

As the network grows, those details will change. New users may want to confirm when independent nodes appeared, which security limitations were known at each release, what the original test vectors showed, and whether later claims differ from what was published before an audit or protocol upgrade.

GitHub can preserve source commits, but the project’s website, transparency page, documentation and public explanations can still be replaced or revised.

Is there a tamper-evident public journal where Quantum-Lattice records every official security disclosure, test-vector release, decentralization milestone and protocol commitment while preserving the original entries permanently? I would like to review it, so please provide the exact URL if it exists.