QNET – Telegram
QNET
377 subscribers
41 photos
13 videos
70 links
Quantum Blockchain
Download Telegram
Finished working on transactions - everything functions exactly as designed. Emission, reward claiming, transfers, fee distribution to block producers - each step goes through the full signature and consensus validation cycle.

Updated the website with current project information and launched the Explorer - you can now track blocks, transactions, and network status in real time.
https://explorer.aiqnet.io/explorer
🔥1553
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.
🔥1576
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.
🔥162🙏21
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
🔥1583👌2🤡1
QNet activation code - public by nature, secure by design.
Code = XOR(wallet, SHA3(tx_hash:type:amount)) - yes, anyone can technically reconstruct it from public Solana data.
But it's useless without:
- Dilithium3 (post-quantum) signature with your private key
- Code embeds your wallet prefix - someone else's code won't match your wallet
- 1 wallet = 1 node enforced in persistent storage forever
The secret isn't the code. The secret is your private key.
🔥2354👍1
Finished developing activation code recovery and the full node activation flow for light nodes — everything works smoothly. Next up: testing light node pings and reward distribution. After that, server node activation, then testnet launch.

https://explorer.aiqnet.io/explorer/tx/def848df0d84071ea2aad3fe4e499c4fd3b50d23a9c0a21b417ef96924fd6bd3
🔥1532
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
🔥11104
This media is not supported in your browser
VIEW IN TELEGRAM
Here is what code recovery and Light Node activation look like on a real device
🔥1631😁1
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.
20🔥82❤‍🔥1👏1