QNET BLOCKCHAIN

QNet Blockchain update QNet Wallet 1.3.1 (32) is out on iOS: testflight.apple.com/join/Ee… The Android update is right behind it and will be live very soon: play.google.com/store/apps/d… • A redesigned app: a fresh look on every screen, with icons in the tab bar and for every token • Token details: each token now has its own screen with its balance and information • Token sending is fixed and simpler: Send opens a list of your tokens with a search, and the token you pick opens its own form • The Node tab shows a light or super node steadily, as the network names it • Move to wallet takes the whole node balance in one press and shows what reached the wallet • After a wallet is deleted the welcome screen opens; after a reset, the recovery phrase screen opens aiqnet.io • The whole site now speaks 11 languages • Connecting the site to the phone app is steadier: requests reach the wallet reliably and wait out a slow connection instead of failing • A new explorer: latest blocks live at the top, search with suggestions, network readouts, and token pages with their holders • My node shows your node, its status and its earnings at a glance, and an activation spends nothing until the network confirms the wallet has no node • Pages open faster and stay readable on any screen The QNet Wallet browser extension 3.1.7 is in review and will be updated soon: chromewebstore.google.com/de…

Big update: aiqnet.io and QNet Wallet have a completely new design. The site, the explorer, the node cabinet and the wallet app were redesigned from scratch in one style. Please make sure the current version is installed: - iPhone: QNet Wallet 1.3.1 (31) in TestFlight - Android: QNet Wallet 1.3.1 (31)

QNet Wallet is now available for testing on iOS! Install TestFlight and join the beta using the link below or enter the invite code EeBbs439: testflight.apple.com/join/Ee… Node setup guide: Telegram: t.me/AiQnetLab/186 X: nitter.gq/AIQnetLab/status/21106… If you encounter any difficulties during activation, feel free to join the QNet community chat for help: t.me/QNET1DEV Join us in testing QNet Wallet!

While the new QNet Blockchain app build waits for approval in the stores on iOS and Android, here is the full node activation done with nothing but a phone or tablet.

QNet Wallet for iOS Final preparations are underway to start testing the non-custodial post-quantum wallet for QNet Blockchain on iPhone and iPad. Waiting for it on iOS and for testing to begin?

Dashboard, Mobile Apps & Extension I am almost done with a major update for the dashboard and mobile apps. Here is what’s new Web-Based Node Activation: Node activation has been moved to the website to prevent token burning inside the app from being classified as an In-App Purchase. Past Epoch Insights: Added detailed historical data for past epochs — you can now view device responses and earned rewards for each epoch. Device Re-linking: Implemented a feature to re-link a device via the website if you change or lose your gadget. Browser Extension Enhancements: You can now connect to the site and partially complete the activation process directly through the extension. I am currently testing all the new features. Everything is expected to be ready by early next week, right after which I will release the iOS build on TestFlight.

👀

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.

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.

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.