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.

QNet - what's been done this round

Three weeks on reworking consensus.

The cause of the stalls was a class of bug, not a single one. Some consensus decisions depended on what a node happened to hold on its own disk rather than on the block height, so two honest nodes could derive different participant lists and diverge - finality stopped with no attacker involved. Every such place is gone: elections are now a pure function of confirmed data, identical on every node. Alongside that, the specific epoch-boundary mechanisms: the participant set was sampled at the boundary while activity proofs stay admissible for another 90 blocks, the "is emission due" check returned a false yes at the very first boundary and the chain stopped ~4 hours in, and nothing actually required the emission at its height - a producer that couldn't build it shipped a valid empty block and the epoch lost both the issuance and its reward root.

A stall is no longer a dead end. Before, when finality stopped, production died three minutes later and there was no way out: recovery needs fresh activity proofs on chain, and those can't get there while production is stopped. Now the network keeps producing for ~48 more minutes on a frozen participant set that is identical everywhere, with no risk of splitting into two chains, and the set shrinks to drop the silent ones so the quorum threshold becomes reachable again. To be straight: making stalls impossible isn't achievable in any network of this type - if more than a third go quiet, finality stops, that's mathematics. What's removed are the reasons we stalled.

One nasty find. An honest producer that re-issued a block after a rollback could be banned on chain permanently, with no attacker present. And the reverse: a small detail in signature parsing let anyone fabricate a valid ban against any producer, and two of those were enough to stop finality for good. Rewritten.

Entry had a hole. Activation codes are tied to a wallet, but that check lived in the application, not the chain - a hand-built registration transaction sent straight to the network bypassed it. And the attestation step signed a binding to whatever beneficiary the caller named, with nothing proving they owned the wallet that actually burned, so anyone who saw a public burn on Solana could collect a legitimate quorum naming themselves. Ownership is now proven cryptographically on chain, and one burn activates exactly one node - previously a single entry could bring up both a super and a light node.

Rewards split 25/75 between operators and users.

Scale and hardening. Consensus messages went from ~3 MB to under 2 KB, registration attestations are collected in parallel (without it, onboarding at scale physically couldn't finish in time), the reward computation fits in memory for millions of recipients, and the state tree moved to disk. Around 250 places closed where a single request could take a node's process down; key substitution over the network removed; transport bound to its session against replays. Claiming rewards now requires the recipient's signature - an unsigned request could previously strip a wallet of all past earnings irreversibly. Storage rewritten: competing blocks at the same height are kept rather than discarded, and every check that quietly returned a partial result on a read error now stops instead of computing a wrong root.

As you may have noticed, rewards are now split 25/75 between operators and users.

The distribution model has been reworked in favour of server nodes. There are orders of magnitude more light clients than operators, and under an even split a server running around the clock earned the same as a phone. A separate share for operators brings the reward in line with what they actually carry. It barely affects users - precisely because there are so many more of them.

Beyond that, super nodes will require a mandatory stake - QNC locked for as long as the node runs.

This also creates the first real market for QNC: light clients earn it, prospective operators need it. Closer to that point I'll open a venue for direct peer-to-peer deals between people looking to buy or sell at the early stage.

First I run in the current system: the network runs, onboarding works under the current rules, node updates work. Then I relaunch with the stake - with the terms published in advance.

I measured QNet's real TPS. Here's the honest number — and why my old numbers were wrong.

The throughput figures I published earlier were what most chains actually publish: a lab benchmark — one node, localhost, transactions pumped straight into the engine, no network between machines, no finality. That measures how fast a single process can chew transactions. It's not a blockchain number. I've dropped it.

What I measured instead. A live 5-node testnet on ordinary budget VPS (~€10/month class; the weakest are plain 8-vCPU machines with slow disks) — real network gossip between five independent machines, producer rotation every 30 blocks, failover armed, post-quantum signature verification on every node, deterministic re-execution of every block by every validator, a Merkle state root every block. A transfer only counts when it is finalized by a BFT checkpoint — not when it lands in a mempool, not when it's merely included.

Result: 13,000 finalized transfers per second, sustained for 10 straight minutes. 99.8% of everything submitted was included AND finalized, on 1-second blocks (the 12k rung ran 932 blocks in exactly 932 seconds), hard finality ~109s median. Peak in 5-minute windows: 16,000/s. Push harder and the network degrades gracefully — it queues and self-drains, no forks and no network halt. 13k is the honest sustained ceiling of €10 machines, found by stepping the load up until it broke and confirming the last step that held.

Single transactions (one post-quantum signature each): ~450/s on this hardware. Not a design flaw — the price of quantum safety. An ML-DSA-65 signature is 3,309 bytes, and no standardized batch verification exists for ML-DSA — each signature verifies individually. For scale: one such signature doesn't even fit in Solana's 1,232-byte packet.

This is where QNet's architecture earns its keep. Batch transfers put up to 1,000 payments under ONE post-quantum signature — 3.3 bytes of signature per transfer. Every batch is signed and verified with plain, unmodified FIPS 204 ML-DSA — no custom crypto, the signature simply covers more payload. That's what makes PQ crypto practical at scale today, and it's why a network of €10 VPSes moves 13k quantum-safe transfers a second while a PQ-retrofitted classical chain would manage an estimated ~2-4k.

Potential: signature verification and block application scale with CPU. On Solana-validator-grade servers the same code projects to ~5k singles and 40-80k batched transfers per second.

What's next. The rolling node-update system and super-node onboarding are done and hardened. What's left is consensus soak-testing: if it runs clean for several days straight, I'm opening the testnet. The LLC is also nearly ready — which unlocks publishing the mobile apps to the stores.
Every number above is reproducible end-to-end over public RPC: submit → include → finalize.

Everyone interested is invited to participate in the testnet again. To do so, you need to install the application attached to this post.

Next, import an existing wallet or create a new one, visit the https://aiqnet.io/testnet page, enter your Solana address in the "Token Faucet" section, and obtain the 1DEV and SOL test tokens.

Afterward, go to the "Activate" section, select "Light Node," click "Get Activation Code," and copy the code provided. In the "Node" section, click "Activate Node" and paste the copied code.

Instructions for users wishing to deploy a Super Node will be published shortly.

Currently, the test network has stopped releasing blocks. I’ll tell you what happened.

When a new light node registers on the network, all nodes must calculate the checksum of the node registry in the same way. It turned out that the node that had itself issued a block with such a registration calculated it differently from the others. It stopped matching the network in terms of the same number and could no longer confirm blocks.

Two light nodes registered. The first one disabled one node, the second one disabled the second one. After that, four out of the five required nodes remained, the confirmation stopped, and the network automatically suspended production. This is a standard safety feature: it’s better to stop than to diverge.

The data is intact. The entire history is in place, and the records are the same for all six nodes. Only one calculated value diverges, and it can be restored by recalculating it.

What I do: I restore agreement on the two affected nodes, fix the cause in the code so that this doesn’t happen again during registration, and update all the nodes.

As I mentioned earlier, a bug was discovered due to the Light Node registration, and I’m currently fixing it. I even had to roll back the network slightly, so most of the registrations were lost. Don’t worry - all of this will be fixed, and the testnet will continue.

The network had some downtime. I'm fixing the causes now: some fixes are already live, and the rest ship in the next update. The network is running, and blocks are being produced and finalized.

Why blocks are faster right now. In QNet every block is tied to its own second since the network launched. While the network was down, time kept moving but no blocks were produced. The network is now producing blocks for the missed seconds, at about 4.5 blocks per second instead of 1. Once it catches up with real time, it returns to 1 block per second on its own.

What you may notice. The explorer shows the latest block times behind real time; this is expected. Reward periods of 14,400 blocks now take about an hour instead of 4 hours, so rewards come more often.

What's next. I'm preparing an update so that after any future downtime the network continues from the current time instead of catching up.

QNet Wallet 1.1.2

This Android update is about correct operation: fees, token transfers and light-node pings now work exactly the way the network expects.

Correct fee. The app now shows and charges exactly what the network debits: 0.00015 QNC per QNC transfer. It used to show a lower number, so the "Total" didn't match what was actually charged.

MAX works for QNC. It leaves the fee on the balance, so sending everything no longer fails with "insufficient balance".

Token transfers are applied. Token transfers used to carry a gas limit below what the network requires: the node accepted them, but they never made it into a block. Gas is now set correctly, and the app checks in advance that there is enough QNC for the fee, plus a refundable 0.01 QNC deposit if the recipient doesn't hold that token yet.

The fee can't be raised in transit. Contract transactions are signed over their gas price and limit, so a node relaying them can't increase the fee.

Light-node pings are answered reliably. Answers go out one at a time, and no request hangs without a timeout.
Interface. Input windows stay above the keyboard, the node activation window matches the others, values on the Node tab are no longer cut off, and the seed phrase warning is highlighted.

Light-node rewards. The network nodes have been updated too. A bug that could cost a light node its reward for an epoch even after it had answered the ping is fixed, so answered pings should no longer lose rewards.

QNet testnet update

The network keeps running clean - one block per second, no stalls.

If you run a light node on your phone:

Minimize the app and lock your screen whenever you like. Liveness pings are answered in the background.

Just don't force-close the app. A closed app can't answer.

Rewards accumulate on chain and nothing is ever forfeited. Claim them whenever you want.
An epoch is 4 hours, and an epoch's reward arrives one epoch after it closes.

A node only reads as inactive after two closed epochs with no answered ping - 8 to 12 hours of silence. Coming back is one tap: "I'm Back - Reactivate Node".

The number of participants keeps growing - slowly, but steadily.

I'm still waiting on the LLC paperwork before the apps can be published officially. I understand that an official release is what earns real trust in the project, and that trust is what brings more people in.

And as promised, very soon I'll start work on the first mini apps, so the network's tokens have somewhere to be used.

QNet Wallet 1.1.4

Wallet:
Transaction history no longer disappears. It is assembled from the explorer archive and the node, paged, and survives the pruning of old blocks on nodes.

Every operation — a transfer, a token send, a reward claim, a node activation — ends on the same full-screen result. Claims used to confirm in a small pop-up.

The hash on the result screen opens the transaction in the explorer; a long press copies it. History entries open the explorer too.
History can be filtered by asset: all, QNC, or a single token.

A transfer to your own address shows as its own type, "Sent to self" — no minus, fee shown; the balance no longer deducts an amount that never left.

If the network does not answer a send in time, the wallet no longer says "failed". It shows the transfer as awaiting confirmation and settles the outcome from the chain itself; sending again cannot charge twice.

The fee shown is exactly what the chain debits; token calls size their gas by the call.

Network and rewards (live already, no update needed):
A phone's answer counts for the epoch the ping was sent in, even when it arrives minutes late because of sleep mode or a delayed push. Such answers used to be discarded and the epoch went unpaid.

An answer that reaches a node outside its shard is delivered to the shard's owners — the signature is no longer lost.

The per-address ping limit is raised: one carrier IP can front many phones.

In the reward history, a zero is no longer labelled "shard not certified" — it shows the real reason.

Transaction and reward history survive block pruning: every node keeps a self-proving epoch archive.

Sending to your own address always worked on chain, only the fee is paid. The old wallet just showed it wrong in history and in the balance. 1.1.4 fixes that, and now they show as "Sent to self". There's no real reason to do it, except testing.

Many noticed the changes on the site: the legal entity is complete and all papers are in hand. The Apple developer application is submitted and under review; the Android release is being prepared in parallel. From here it is up to the platforms.

Exactly one year ago the 1DEV token launched and our community was born. The development itself started earlier and has been going on for more than a year and a half.

For all of us it was a hard but truly fascinating year — a year that tested faith and patience. There were plenty of questions, and all of them were fair. Can the developer turn words into reality? Isn't this just another larp? When is the testnet coming? Far from everyone made it to this day, when the biggest of those questions are behind us. And I understand everyone who had doubts.

For me, this year and a half has been a test of strength, both physical and mental. I bet everything on this project.
Day after day of 16-hour work, lack of sleep, stress, psychological pressure and responsibility — for the result and for everyone who believed. Mistakes I had to fix. Plus 20 kilograms and a couple of other "non-critical" health consequences. All the money I had. And an endless belief that it would work out. I'm not bragging, but I honestly don't know whether anyone else has worked on their project this much and this meticulously. I know one thing: I gave it everything.

Why all of this?
I've been deep in crypto since 2019. I saw the rise and fall of retrodrops, took part in ambassador programs, hunted NFT whitelists on Discord and token-sale whitelists, joined token sales, ran nodes, wrote articles. I was one of the first users of pump.fun — back when a token with a website and socials already counted as a gem, funny to remember now. I caught the Telegram tap-to-earn games too.

Over those years I learned the main thing: an early user almost always plays a lottery, and most of the time it isn't in their favor. You put in time — first of all time — and money, and end up with nothing.

Blockchains are no different. Almost every new network launches with the same playbook: investors, a premine, private rounds you're not part of, and an airdrop lottery for those who came first and gave it activity. There are also projects with a structure similar to ours — I didn't even know they existed when I started. But some of them still haven't left testnet, while the premine and everything else is already in place. Others hand out points instead of real rewards. That approach isn't for me. I want to bring back that spirit of crypto enthusiasm and give this space a new turn — something clean and original.

That is the essence of QNet: rewards go to those who take part in the network, not to those who got into a round. You don't need a server — a phone with the QNet mobile app is enough. The app answers the network, and every 4 hours its owner is credited with a share of the emission. Not points and not an airdrop promise, but on-chain tokens from day one, under the same rules for everyone.

Some pump.fun projects and post-quantum networks mention QNet, jump into discussions, and their supporters promote their projects in our comments. That's normal. But I don't see them as competitors. Most of them are no different from thousands of others, except for tweaks to consensus. And users don't care what consensus runs under the hood: they need things to work correctly and reliably. A copy of something that already exists, with one feature of its own, doesn't become something new. And price shows nothing here — just like in contemporary art. The truth isn't in how much a project is worth, but in what it brings to people.

I know not everyone likes my methods, my openness on some matters and my reticence on others. But I don't live by other people's made-up rules. I've always been stubborn and done what I believed was right — by my conscience and my convictions. When this idea came to me, I didn't ask myself whether it would work. I just sat down and started building, and didn't let doubt settle in my head.

"Don't tell me what I can't do"

And now the main thing.
QNet works. Not in a pitch deck and not in promises — on the network. Since August 31 it has been running on a single genesis: more than 3 weeks without a restart from scratch. There were halts at the start; they were investigated and fixed, and since September 15 the network has been running without a single stop. 1 block per second, over 2,000,000 blocks already. 6 super nodes and 60 registered light nodes on ordinary phones, 40 to 48 of them online in each epoch. Every 4 hours the network itself distributes rewards to those whose nodes were online. No investors, no funds: QNC comes only from emission.

None of this would exist without you. Without the people who believed and still believe, this path would have been impossible. Thank you to everyone who stays with the project: for ideas, for posts, reposts and likes on X, for messages in Telegram, for being part of the group's life, for testing the app and the network. I see everyone who promotes the project, I follow it closely, and I truly value that work.

A special thank you to the person who has my back and carries the communication in our community — Raji. Without his crazy dedication, energy, faith and enthusiasm, our community would be impossible to imagine. In hard moments he found the right words, and when it was needed, strict ones, to keep the right atmosphere in the group. Thank you.

There's still a huge amount of work ahead: a token lock for super nodes, mini-apps, smart contract testing, releasing the apps in the stores, and bringing the project to the masses. There are still open questions with the stores, but I'm sure they'll be resolved just like all the others. After the apps are released, I'll most likely launch a content contest with a cash prize pool. And once everything is stable and the project catches the wave, I'll grow the team: carrying something this big alone is, to put it mildly, hard. For now the focus is on the nearest tasks, and decisions will be made as the project grows.

After the road already traveled, all of this feels small. I have no doubt that every task will get done.
We're already here. We've already done it. Now it's time to grow, and everything else will come in time.

Happy first year, QNet. And congratulations to everyone who made it to this day.