Telegram RegisterThe public register of Telegram
Telegram profile photo for QNET

Channel

QNET

@AiQnetLab

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

384subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002614001365
TypeChannel
Username@AiQnetLab
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/AiQnetLab

Growth

384387385.57 August 2026 — 386 subscribers8 August 2026 — 386 subscribers14 August 2026 — 387 subscribers22 August 2026 — 384 subscribers7 August 202622 August 2026
4 measurements spanning 14 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 384–387 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 04:05384-3
14 Aug 2026, 21:37387+1
8 Aug 2026, 06:04386no change
7 Aug 2026, 17:24386first reading

Engagement

20 posts held, back to 23 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 58s
Average length
39s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

520 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 44.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
23044.2%
🔥19337.1%
5510.6%
👍173.27%
👀71.35%
🙏50.962%
👏30.577%
🎉20.385%
💯20.385%
🤝20.385%
🍾10.192%
😁10.192%
🥰10.192%
🫡10.192%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 520reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 23 February 2026 to 22 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

22 Jul 2026, 02:51 UTC252 views27 reactionsread 8 August 2026

“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.

16🔥7👀21🥰1

20 Jul 2026, 04:46 UTC274 views21 reactionsread 8 August 2026

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 t

12🔥6👍3

20 Jul 2026, 04:13 UTC252 views24 reactionsread 8 August 2026
Photo

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 genes

14🔥81👍1

7 Jul 2026, 05:24 UTC397 views41 reactionsread 8 August 2026

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 a

31🔥6💯21👀1

5 Jul 2026, 07:03 UTC414 views19 reactionsread 8 August 2026

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.

145

5 Jul 2026, 06:46 UTC399 views12 reactionsread 8 August 2026

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.

👍82🔥2

5 Jul 2026, 05:29 UTC423 views20 reactionsread 8 August 2026
File

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-

🔥1451

4 Jul 2026, 06:42 UTC341 views25 reactionsread 8 August 2026
Video

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

🔥166👀21

29 Jun 2026, 10:07 UTC459 views27 reactionsread 8 August 2026
Photo

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

🔥194👀21🙏1

28 Jun 2026, 14:22 UTC417 views25 reactionsread 8 August 2026
Video

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

77🔥6👍3🤝2

26 Jun 2026, 15:31 UTC335 views38 reactionsread 8 August 2026

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.

30🔥51🍾1🙏1

Showing the 12 most recent of 20 posts we hold for @AiQnetLab. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 22 August 2026 — this entry's latest reading, not the date you are reading this.

“QNET” (@AiQnetLab), 384 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/AiQnetLab.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.