💎 Toncoin → Gram The rebranding is in progress 🔥
❤14❤🔥10💘3👎2

Channel
@tontech
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
24,995subscribers
-138 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001764902466 |
|---|---|
| Type | Channel |
| Usernames | @thetontech @tontech |
| Created | 8 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/tontech |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:03 | 24,995 | -12 |
| 12 Aug 2026, 11:37 | 25,007 | -14 |
| 11 Aug 2026, 23:31 | 25,021 | -9 |
| 11 Aug 2026, 10:13 | 25,030 | -6 |
| 10 Aug 2026, 22:54 | 25,036 | -13 |
| 10 Aug 2026, 10:20 | 25,049 | -5 |
| 9 Aug 2026, 19:51 | 25,054 | -4 |
| 9 Aug 2026, 13:11 | 25,058 | -28 |
| 8 Aug 2026, 20:02 | 25,086 | -3 |
| 8 Aug 2026, 13:14 | 25,089 | -16 |
| 7 Aug 2026, 19:20 | 25,105 | -8 |
| 7 Aug 2026, 14:14 | 25,113 | -10 |
| 6 Aug 2026, 22:07 | 25,123 | -3 |
| 6 Aug 2026, 16:52 | 25,126 | -7 |
| 6 Aug 2026, 02:02 | 25,133 | +1 |
| 6 Aug 2026, 00:52 | 25,132 | -1 |
| 5 Aug 2026, 22:02 | 25,133 | first reading |
20 posts held, back to 14 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof 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 15 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
550 reactions across 20 posts, in 23 distinct kinds. The most used accounts for 22.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 124 | 22.5% | |
| ❤ | 96 | 17.5% | |
| 🔥 | 76 | 13.8% | |
| 🏆 | 49 | 8.91% | |
| 👍 | 44 | 8.00% | |
| 👏 | 43 | 7.82% | |
| 🦄 | 39 | 7.09% | |
| ✍ | 11 | 2.00% | |
| ⚡ | 9 | 1.64% | |
| 🤝 | 9 | 1.64% | |
| 🤯 | 9 | 1.64% | |
| 👎 | 8 | 1.45% | |
| 👨💻 | 7 | 1.27% | |
| 🆒 | 5 | 0.909% | |
| 😨 | 5 | 0.909% | |
| 💘 | 3 | 0.545% | |
| 💯 | 3 | 0.545% | |
| 😡 | 3 | 0.545% | |
| 🎉 | 2 | 0.364% | |
| 😎 | 2 | 0.364% | |
| 3 further kinds | 3 | 0.545% |
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 550reactions 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 14 April 2026 to 15 June 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.
💎 Toncoin → Gram The rebranding is in progress 🔥
❤14❤🔥10💘3👎2
TON Connect Bridge v3. The new bridge introduces horizontal scaling and shared infrastructure for the entire ecosystem. Wallets once again operate through a unified bridge, while developers get end-to-end observability from a click in a dApp all the way to a signature in the wallet. Intro • 1 • 2 • 3 • More TON Tech • 𝕏
❤🔥9🔥7👏5⚡1👍1👨💻1
Gasless transactions. Applications can now cover transaction fees for users and accept payments directly in jettons. For example, a user can buy something with USDT even if there is no TON in their wallet to pay for gas. Intro • 1 • 2 • 3 • More TON Tech • 𝕏
🏆9👍7🔥5❤🔥3😡1
Read more about all the updates, including new dApp scenarios, Structured items, Trace ID, the new Demo App, and AppKit and WalletKit improvements in the full article. Intro • 1 • 2 • 3 • More TON Tech • 𝕏
🔥13👍8👏5❤🔥3⚡2🏆1
Embedded requests. Wallet connection and action execution can now be combined into a single flow. Instead of switching between the app and wallet twice, users can confirm both the connection and the transaction on a single screen. Intro • 1 • 2 • 3 • More TON Tech • 𝕏
👏9👍6🔥5🤩1🆒1
TON Connect v3. TON Connect has received a major update with gasless transactions, connect-and-action flows in a single step, and new tools for working with jettons and NFTs. Read more about the update Intro • 1 • 2 • 3 • More TON Tech • 𝕏
🔥7🏆5❤🔥3👨💻1😁1🆒1
🪙 Toncoin Name Change — Community Vote TON has changed substantially in recent months. Telegram is taking on a leading role in the network and is becoming its largest validator. The chain itself is now 10× faster with fees down 6×. Gram was the name the network's founders gave the token in the original TON White Paper, and it's never left the codebase. That is why Telegram is proposing to rename the native token fr…
🔥8❤6❤🔥4👏2
docs.ton.org — updated structure, improved search and much more TON Tech team shipped a major documentation update. Here are the highlights: — new navigation built around developer flows — dedicated Applications section for AppKit, TON Connect, TON Pay and WalletKit — redesigned TON Center API reference — new search with proper prioritization — llms.txt and markdown endpoints for AI agents — hundreds of DX and UX f…
👍13❤🔥8❤7⚡2🔥2👨💻1🆒1
TON developer documentation has been fully updated Now everything needed to build in TON ecosystem is gathered in one place: — smart contract documentation — application development flows — SDKs and tools — general documentation for TON blockchain Navigation is now much simpler, the structure is clearer; finding what you need is way much faster. Click to see fully revised TON documentation
❤17👏14🦄8👎6💯3😡2⚡1
Hi, we’ve got a small dev inbox experiment here We’re constantly building tools for TON — WalletKit, AppKit, TON Connect, AI agents and all that good stuff. And the more we build, the more new use cases and developer questions we see that are not always obvious upfront So we’re opening a dev open mic for the community. Simple format: you drop a question → I answer as an engineer, not as a press release. If a questi…
❤12❤🔥9👍4🔥3🤝2🆒1
Why different staking protocols in TON show different APY? After the sub-second update, validator rewards increased ~6x. Previously, different calculation models could show values like 4.19% and 4.28%, while after the update they show ~25.44% and ~22.83% depending on the formula and reward accounting mechanics. Let’s briefly break down where these numbers come from and why they differ. In TON, staking works in cycl…
🏆7🔥6🤯4❤🔥2✍1🤔1
🏁 TON leads Layer-1 blockchains in finality time. 🔗 Sources: https://telegra.ph/Comparison-of-Layer-1-blockchains-by-finalization-time-05-01
🏆9❤🔥8🦄5
Showing the 12 most recent of 20 posts we hold for @tontech. 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 — 58,756 of 1,151,006entries 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.
Named by 17 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
“TON Tech” (@tontech), 24,995 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/tontech.
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.