Still working on the app. Latest focus - backend fixes and background pings: your node stays active even when the app is closed or the screen is locked. Open the app once - the network handles the rest.
No commits ≠ no progress. Not everything goes to the repo right away.

🎂 Exactly one year ago, I wrote the first lines of QNet Blockchain code.

Over this time, I went through many AI models - each one better than the last, helping me solve problems faster and more efficiently.

I want to repeat the core idea once more, because it truly matters.

I wanted to build a system that rewards every user - constantly and automatically. When I started, I had no references, no other project attempting anything like this. And today, I still haven't seen a single one moving in this direction.

QNet is:
- No premine. Every participant gets an equal share after activation.
- No technical knowledge needed. A couple of taps on your phone screen - that's it.
- Rewards accumulate automatically. Hit claim whenever you want - no daily grind, no tapping required.

Think of the legendary early Bitcoin faucet - but permanent, effortless, and accessible to absolutely everyone.

This is the blockchain approach I always dreamed of. And we're on the final stretch.

A few finishing touches remain in the consensus mechanism - and the user reward system will be fully complete. Very soon.

And once again - a huge thank you to each and every one of you. Without your support and engagement, reaching this point would have been incomparably harder.

More to come 👀

Huge block of tasks done.

Completed the full light node cycle for QNet. Everything works now - from wallet creation to receiving rewards for participating in the network.

How it works:
Burn 1DEV - get a spot in the network
App registers the device on-chain
Every 4 hours the device sends a ping - proof of participation
At the end of an epoch - rewards are accrued
One-tap claim - tokens in the wallet, send anywhere

The video shows the real thing: claiming light node rewards and transferring QNC to another wallet.

Here's how light node proof-of-participation works in QNet.
Every 4 hours the network checks whether your device is online. This isn't a simple ping - it's a cryptographic challenge-response.
How it works:
Each 4-hour window is split into 240 one-minute slots. Every node gets a unique randomized slot per window, derived from a hash of the node_id and window number. You can't predict in advance when the request will arrive.
When your slot hits, a genesis node sends a challenge - a random 32-byte string - to your device via push notification. The device signs it and sends back the response.
Three attempts, not one. If the primary genesis node doesn't get a response, two backup nodes retry with a delay, giving the primary time to complete first. Miss all three - the round is skipped. After 5 consecutive missed rounds, the node is marked inactive. There's a reactivate button in the app to bring it back.
The ping key is separate from the wallet. At registration, the device generates a dedicated Dilithium3 key specifically for signing ping responses and issues it a delegation certificate signed by the main wallet key. This lets the app respond to challenges in the background even when the screen is off or the app is closed - the main wallet key is never touched.
The response is signed with this delegated Dilithium3 key. The attestation is then propagated to all genesis nodes via gossip protocol.
Rewards aren't instant. Participation data is collected into a MacroBlock at the end of the epoch, and payouts happen one epoch later - 4 hours after the window closes. This is an intentional delay to allow finalization through BFT consensus.

Hey everyone - it’s been a few quiet weeks on the feed, but development has been moving steadily behind the scenes.

What’s been done:

- Server node registration is live and working
- Synchronization logic with the network is nearly complete
- Reactivation logic implemented - nodes now handle reconnects correctly after migrations or long offline periods (same nuances as mobile nodes, just different complexity)
- Security audit done: a vulnerability in the network was identified and patched

What’s left:

Finishing server node integration + polishing the node update mechanism. We’re close - genuinely the last stretch before testnet.

Thanks for your patience. It means a lot.

Testnet is coming. Soon.

Super-node onboarding is finally complete - along with a lot of other work I'll share more about soon.
Now it's time to observe and test how the network runs after onboarding.
I'm genuinely happy to finally have visible progress to show, and to share it with you.

QNet - what's been done over the last 3 months

It's been quiet - because the work went into rebuilding the foundation, not cosmetics. The facts:

1. Consensus core rewritten → Checkpoint-BFT v2
The old macroblock consensus was three-phase (commit → reveal → finalize) with fixed ~12+12+6 sec windows and heavy post-quantum signatures collected at every phase - both slow (~30 sec per macroblock) and fragile (desync at phase boundaries → occasional forks and stalls). Replaced with a single-round Checkpoint-BFT v2: instead of three phases, one 2f+1 quorum certificate (QC), with no fixed windows and no dependence on clocks; producer selection is deterministic, and forks are impossible by construction. Post-quantum BFT on Dilithium / ML-DSA.

2. Scale - to millions of nodes
Emission and the node registry were rewritten to O(1) operations (previously the cost grew with the number of participants). The architecture is designed to hold millions of light nodes and super-nodes without degradation.

3. Security
Several audit rounds (120+ fixes), node identity-binding, and fail-closed key handling from the mnemonic.
4. Node onboarding
Solved the problem of a new node joining a live, running network without disruption. The first real super-node is connected.

By the numbers:
150 commits
168 files changed (21 new, 1 removed, 145 reworked)
+53,611 / −38,944 lines

Huge thanks to everyone for your patience. What's left: test reward claiming by a super-node, finish the node-update mechanism, and run my own final audits before the testnet launch.

Testing the full integration of a super-node with the mobile app - including reward claiming - and debugging all the processes.

Super Node rewards are LIVE.

Claim and receive your QNC rewards straight from the mobile wallet - one tap, on-chain verified, post-quantum secured.

QNet Wallet - early access on Android (APK)

I've decided to open early access for light nodes - just through the APK. That gives you a few days to test it out while I finish a round of fixes: audit items, plus removing all the non-quantum signature paths that blockchains normally use, so QNet stays fully post-quantum.

On the official launch: I've set up an LLC and I'm waiting on the documents to finish Apple's D-U-N-S verification. Once that paperwork clears, QNet goes live officially on both Google Play and the App Store.

Test tokens: https://aiqnet.io/testnet

Made a wallet during earlier testing? Create a fresh one - the wallet format changed, so old wallets may not import correctly and can come up invalid.

Important: In the faucet, enter your Solana wallet address - not your QNet address.

Then, in the mobile app, select Light node and tap Get activation code.

Once you receive the code, go to the Node section and tap Activate node.

Strange - it looks like the current activations aren’t going through on-chain. I’ll look into what’s causing this.

Going forward, when the network is restarted, those who have already burned and activated will only need to restore their activation code. Re-burning coins won’t be necessary.

I’m closing this topic for good - but first, I want everything to be completely clear.

I fund all of the development myself. Servers, AI tools, domains, company registration - I pay for all of it out of my own pocket. The only income this project currently brings me is the trading fees on pump fun. And right now, that isn’t even enough to cover development costs together with the bare minimum for rent and food.

I am an investor in this project just like you are, and I have never claimed that I wouldn’t sell my own tokens. Once every two weeks I sell a small portion - around 1 million tokens. This is not a dump, and it is not market manipulation. It’s what allows me to keep working on the project instead of looking for income elsewhere. And I do it openly, in plain sight, not through separate wallets.

For a year and a half I have lived this project - no days off, months on end, giving it everything I have. If someone believes I’m obligated to follow unwritten rules I never signed up for, that’s their right. But my responsibility lies elsewhere: to see this project through. And to do that, I need to stay standing - both physically and mentally.

Now, about what actually matters.

This project is my creation and one of the main goals of my life. I’ve already brought it almost to MVP, and I will see it through no matter what. That is not up for debate.

I’m genuinely grateful to everyone who holds and understands that there is real work behind this, not empty promises. It’s your support that keeps me from burning out on the final stretch. We’re already close - and I intend to make it. Thank you for being here.

QNet - testnet status

The previous testnet run stayed up for a few days and then stalled: in a rare scenario at an epoch boundary, finality stopped advancing and the network couldn't recover on its own.
So instead of slapping on a patch, I'm reworking consensus so this class of freezes is gone at the protocol level rather than papered over. That's the main reason for the delay.

Since I'm starting from a clean genesis anyway, I also folded in the things that can't be added after launch:
• full post-quantum security - ML-DSA-65 (FIPS-204) signatures and post-quantum transport;
• on-chain tokens and smart contracts - a token standard, mint/burn, a deterministic WASM VM.
Where I am now: I'm putting the consensus changes through their paces. The automated tests and audits pass, but the real test is live - new issues can still surface, and I'll fix them as they do. What's left is to bring up a fresh network and run it through many epoch boundaries - exactly the conditions where it used to freeze.

On timing: Once the network runs stably for several days with no freezes, I'll launch and open onboarding for light nodes and super nodes.
Thanks for waiting. I'm choosing the right launch over a fast one.

New wallet addresses in the new launch

I moved the wallet to post-quantum cryptography - ML-DSA-65 (FIPS-204) signatures. Because of that, your address changes.

A QNet address = hash of the public key, and the key is derived from your seed phrase through the signature algorithm. I changed the algorithm → the same seed phrase now yields a different key → a different address. I also fixed a mismatch, so the app and the node now produce the same address.

So in the new launch:
• update the wallet once I post the new version;
• request test tokens again from the faucet - to the new address;
• re-do node activation.

Your seed phrase doesn't change - same mnemonic.

“Reworking consensus” doesn’t mean rewriting it.

The core and consensus are built right - the design stands. The freeze was one rare edge case at an epoch boundary, not a flaw in the foundation. What’s left is closing that gap at the protocol level and catching the remaining edge cases so nothing else can stall the network.

No rebuild, no starting over - just finishing the last loose ends before launch.