Telegram RegisterThe public register of Telegram

Channel

IoTeX Announcement Channel

@iotexchannel

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

26,398subscribers

-579 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001305509002
TypeChannel
Username@iotexchannel
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/iotexchannel

Growth

26,39826,97726,687.56 August 2026 — 26,977 subscribers6 August 2026 — 26,977 subscribers7 August 2026 — 26,915 subscribers8 August 2026 — 26,873 subscribers9 August 2026 — 26,772 subscribers10 August 2026 — 26,675 subscribers10 August 2026 — 26,613 subscribers12 August 2026 — 26,524 subscribers13 August 2026 — 26,398 subscribers6 August 202613 August 2026
9 measurements spanning 7 days, net -579. 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 26,311–27,064 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 02:4826,398-126
12 Aug 2026, 00:0226,524-89
10 Aug 2026, 23:3426,613-62
10 Aug 2026, 00:3126,675-97
9 Aug 2026, 02:1126,772-101
8 Aug 2026, 01:4526,873-42
7 Aug 2026, 04:2726,915-62
6 Aug 2026, 06:0026,977no change
6 Aug 2026, 05:5526,977first reading

Engagement

22 posts held, back to 21 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.09%
avg views ÷ 26,398 subscribers
Avg views / post
551
4 posts measured
Reaction rate
0.863%
reactions ÷ views · ER floor
Posts in window
4
of 22 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held22 (21 February 20269 August 2026)
Views total2,202
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 22:09 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
16s
Average length
8s

Measured directly from 2 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

108 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3633.3%
💯2825.9%
2725.0%
🔥87.41%
🤝76.48%
🌚21.85%

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 21 of the 22 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 110reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 21 February 2026 to 9 August 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

9 Aug 2026, 19:50 UTC365 views4 reactionsread 12 August 2026

Trading for $IOTX perpetuals is now live on Aster DEX! 🚀 As one of the largest onchain perp DEXs with over $3.8T in cumulative volume, Aster brings deep liquidity to the IoTeX ecosystem. ✅ Up to 5x leverage ✅ Fully onchain & self-custodial More venues. Deeper liquidity. More ways to access $IOTX https://x.com/Aster_DEX/status/2086456219745833084

🔥2💯1🤝1

7 Aug 2026, 04:54 UTC486 views6 reactionsread 12 August 2026

IIP-59 is officially coming to a vote on the IoTeX Hub 🗳️ Right now, voter rewards run through Hermes - an off-chain service that holds keys, computes payouts outside consensus, and charges a fee. IIP-59 moves everything directly into the protocol: → No service fees. Voters keep 100% of their yield. → Zero downtime. Rewards no longer rely on external servers. → Enforced by block validation, not by trust. → Optional

💯41👍1

4 Aug 2026, 10:23 UTC529 views6 reactionsread 12 August 2026

Real World AI is no longer just a vision - it’s becoming reality Quicksilver Pro is one of the first products built under IoTeX’s Real World AI initiative, giving developers instant access to the world’s best AI models through a unified API. The momentum has been incredible: we’ve already surpassed 1,000 paid users, and we’re just getting started. Congrats to the team on Day 1 support for Qwen3.8-Max. More to come

4🌚1💯1

14 Jul 2026, 12:39 UTC822 views3 reactionsread 12 August 2026

The biggest AI summit in SF is happening this weekend, and the IoTeX team will be on the ground 🌁⚡ We're looking forward to connecting with the top minds shaping the next era of real-world AI at AGI Summit Who else is heading out? Let’s connect! 👇 https://x.com/agisummitai/status/2074635394243854533?s=20

💯3

8 Jul 2026, 19:58 UTC645 views2 reactionsread 12 August 2026

ioPay 5.8 is here 🚀 Use your favorite dApps with built-in network proxy support — smoother access, better privacy, right inside ioPay 🌐🔒

👍2

19 Jun 2026, 19:52 UTC≈1,100 views6 reactionsread 12 August 2026
Video

Announcing Trio 🏆, a world model for physical operations by MachineFi Lab & IoTeX core team Earlier this year, IoTeX set one challenge: become AI's interface to the physical world. Meet the answer. Trio 🏆 A world model for physical operations - warehouses 🏭, factories, hospitals 🏥. Using cameras and sensors businesses already have. The loop: Perceive → Predict → Act ⚡ Real example: forklift backs up, worker step

5👍1

8 Jun 2026, 22:46 UTC755 views4 reactionsread 12 August 2026

🚨 IoTeX Core v2.4.1 "Yap" Hardfork is HERE! 🚨 Full Ethereum Pectra compatibility has officially landed on IoTeX! ⚡️ What’s dropping at block 48,985,561? ✅ IIP-60 (Pectra EVM): Parity with Ethereum’s latest! Unlocking Account Abstraction (EIP-7702), Rollups, and cross-chain BLS. ✅ Candidate Exit Queue: Safer, predictable validator exits to protect network stability. 💥 A massive leap forward for large-scale DePIN & R

🔥31

22 May 2026, 19:17 UTC734 views3 reactionsread 12 August 2026

IIP-64 is open for discussion: Post-Quantum Cryptography 🛡 Following recent quantum breakthroughs, we're evolving IoTeX's core cryptography from "classical ECDSA" to secure IoTeX against next-gen quantum threats. Here’s the proposal: 🛡Post-Quantum Security — Migrating from secp256k1 to ML-DSA-65 ⚡️Tailored for IoTeX — Optimized for 5s block finality and Roll-DPoS consensus. 💹Proactive Defense — Aligning with NIST s

👍2💯1

17 May 2026, 08:40 UTC≈1,010 views2 reactionsread 12 August 2026

🚨 SCAM ALERT A fake website is pretending to distribute the IoTeX Desktop App The scammers are currently using email notifications to target users and lure them to the site. Block and avoid this domain: iotexdesktopapp .io ❌ Do not download any software from it or interact with the page. Always double-check the URL logic before clicking

👍1💯1

5 May 2026, 18:01 UTC884 views8 reactionsread 12 August 2026

The IoTeX team is heading to Consensus 2026 in Miami 🌴 Our Co-Founder Jing joins Austin Federa and Mike Horton to hype-check the future of decentralized infrastructure. Moderated by Anna Bertha from DCG 📉 AI compute demand: bullish or bearish for decentralized AI? 📈 Date: Wednesday, May 6, 1:50 PM EDT Location: MBCC, Convergence Stage Join us to see how we’re empowering developers to build verifiable, real-world

3💯2🔥2👍1

23 Apr 2026, 20:44 UTC997 views8 reactionsread 12 August 2026
Video

The $IOTX chain is now readable by AI 🤖 http://iotexscan.io/ v4 is now live — a greenfield rebuild designed from day one to be crawled, understood, and cited by AI agents. What's new: ⚡️ Noticeably faster across the board 🔍 SEO + GEO optimized for Google and AI search 🧠 JSON-LD, /llms.txt & JSON APIs — ChatGPT, Perplexity & Claude can cite it directly 🛠️ Modern stack: Bun, Next.js 16, Drizzle, Tailwind The $IOTX c

💯7🔥1

9 Apr 2026, 16:00 UTC880 views5 reactionsread 12 August 2026

🚨 $IOTX Joins Binance LiquidityBoost Program 📈 $IOTX is now officially included in the Binance Spot Altcoin LiquidityBoost Program This program brings in professional market makers to strengthen buy and sell liquidity - improving overall trading performance for the IOTX/USDT pair on Binance Spot. What this means for $IOTX: ✅ Deeper market liquidity for IOTX/USDT ✅ Lower slippage and smoother trade execution ✅ Bett

3💯2

Showing the 12 most recent of 22 posts we hold for @iotexchannel. 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.

Citation-graph rank

Citation-graph rank — 226,881 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“IoTeX Announcement Channel” (@iotexchannel), 26,398 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/iotexchannel.

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.