Architecture & Testnet Update

Removed the second reward pool where transaction fees were distributed among all super and full nodes - realized it was overcomplicating the architecture without adding real value. For the same reason, I removed full nodes entirely, leaving just two types: light nodes (which are essentially clients, not real nodes) and server nodes (super). Simpler is better.

Before launching the testnet, I still need to test user node registration - both server and mobile. Also need to verify how light node ping functionality works end to end.

Once all checks are done and final adjustments made, we can start full-scale testing. At launch, access will be Android-only. iOS support is coming - it just needs time. One thing at a time. Let's get to testnet first and go from there.

Note: the Explorer is live and showing current network data, but the chain will likely be reset several times before the official testnet launch as I make fixes and adjustments. All existing blocks, transactions, and balances will be wiped with each reset.

In the latest big update, I've completely replaced the previous block producer selection mechanism (QRDS) with Dilithium3-VRF - a verifiable random function based on post-quantum cryptography, NIST FIPS 204 (ML-DSA-65).

What this means in practice:
Previously, producer selection was deterministic - all nodes computed the same hash function from public data, and the result was predictable in advance. This created an attack vector: knowing the future producer, an adversary could target them before block creation.
Now each node privately evaluates a VRF using its secret key and a shared seed value. The result is unpredictable to everyone else, yet cryptographically verifiable - any network participant can confirm that the node genuinely had the right to produce the block, without knowing its private key. The winner is determined by the lowest VRF output among all claims, making result manipulation impossible.

In parallel, I'm working on the node activation mechanism. The key security requirement: the activation code is cryptographically bound to the wallet address that received it. This means that even if the code is intercepted, it cannot be used from a different wallet - during server-side activation, an XOR-encrypted binding between the code and the address is verified. The owner's mnemonic phrase is the only way to confirm the right to launch a node.

Not long ago I ran stress tests on the network that showed around 100K TPS - but the problem was that the network broke down afterwards, likely due to issues with the cryptographic signatures at the time.

Since then I reworked the signature system and ran new tests. Results:

- Peak TPS: 54,162
- Average TPS: 53,516
- Transactions: 978,664 out of 999,996 (97.9% success)
- Duration: 18.7 sec
- Errors: 0
- Latency avg: 0.081 ms
- Latency p99: 0.115 ms

The network runs flawlessly after the tests - all 5 nodes are synchronized, 0 forks, 0 errors.

It's possible to push TPS even higher, but that would require expanding the mempool and increasing block sizes, which could cause issues with block propagation and exchange between nodes due to their size. So I prefer to focus on finishing the node registration work for now.

Either way I'm happy with the current 54K TPS - that's an insane result for an L1 blockchain with post-quantum Dilithium3 signatures.

http://162.244.25.114:8001/api/v1/benchmark/results

QNet Testnet - what's on the roadmap?

Want to share a quick update on what I`m planning to ship:

- Token creation tools for users within the QNet ecosystem
- NFT collection launches - fully on-chain
- In-wallet mini-activities - compete with other users, earn $QNC. A little on-chain gambling energy never hurt anyone 🎲

No hard dates yet - these features land after Light & Super Node activations are complete. But they're next in line.

Building doesn't stop

Here is what code recovery and Light Node activation look like on a real device

On March 6th it will be exactly one year since the first line of code.
A year ago I had an idea - a blockchain that puts the user first. Not investors, not funds, not the team. The user. A blockchain where anyone can simply pick up their phone, activate a node and earn native network tokens. No servers, no technical knowledge, just like that.
Over this year I have spent more than $20,000 of my own money. Every month from $2,000, some months reaching nearly $7,000. A few close people believed in the idea at an early stage and supported me financially - I am genuinely grateful to them. But overall this has been my personal journey - thousands of hours of work that turned into a massive technology stack and hundreds of thousands of lines of code.
I want to be honest with you - the same way I have been honest from the very beginning.
The initial 25% token buyout was calculated in part to cover the costs of building the project. For a while pumpfun commissions covered the expenses, but from time to time moments arise where you have to find solutions to keep moving forward. That is a normal part of the journey.
I never said I would not sell tokens. I am an investor just like you. And that is exactly why I do not want to sell right now - current price levels are far from where I would want to do that. But what matters more is this - I do not want to hide sales, move tokens to other wallets and sell from them quietly. I will not play those games with you. Ever.
Everything I do and will do will be transparent. Any sales, whether to continue development or to take personal profit when the time comes - I will do with respect for you and for the market, without hitting the price with aggressive volume.
You came first. You understand the idea at a time when most people are still not paying attention. You are not just an audience to me - you are people I feel responsible to be honest with, and people I genuinely want to see succeed.
When the testnet launches and people see that you can run a node from your phone on a real post-quantum L1 with zero premint - the interest will come naturally. You will have been part of this from the very beginning.
Thank you to everyone who answers questions from newcomers - often the same questions over and over - without losing patience. Thank you for the reposts, likes and original posts. You are building this community alongside me and that means a great deal.
Thank you for being here.

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.