Channel
@toncenter_news
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
927subscribers
+45 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002143019393 |
|---|---|
| Type | Channel |
| Username | @toncenter_news |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/toncenter_news |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 10:15 | 927 | +39 |
| 2 Sept 2026, 01:08 | 888 | -1 |
| 26 Aug 2026, 12:57 | 889 | +7 |
| 20 Aug 2026, 07:26 | 882 | -3 |
| 12 Aug 2026, 20:05 | 885 | +2 |
| 6 Aug 2026, 20:50 | 883 | +1 |
| 6 Aug 2026, 14:22 | 882 | no change |
| 5 Aug 2026, 22:01 | 882 | first reading |
20 posts held, back to 5 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 17 July 2026. An engagement rate over an empty window would be a number about nothing.
166 reactions across 20 posts, in 11 distinct kinds. The most used accounts for 38.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 64 | 38.6% | |
| ❤ | 42 | 25.3% | |
| 🔥 | 32 | 19.3% | |
| 😁 | 12 | 7.23% | |
| 🤝 | 4 | 2.41% | |
| 🤡 | 3 | 1.81% | |
| 🍌 | 2 | 1.20% | |
| 👎 | 2 | 1.20% | |
| 💩 | 2 | 1.20% | |
| 🤩 | 2 | 1.20% | |
| 🤯 | 1 | 0.602% |
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 166 reactions 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 5 May 2025 to 17 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.
New Indexer Database Architecture The database has been divided into three tiers: Hot — transactions from the last 2 week; Cold — the complete transaction history; Key-Value — states, BOCs, and metadata. This makes processing queries to recent data, which account for most of the load, 2–4× faster. The architecture is already used in toncenter.com/api/v3 and will later be available as a standalone build. API V2 H…
❤5🔥4💩1🤯1
Note: There are no changes to the Toncenter API following the renaming of the Toncoin to Gram.
😁11👍7💩1
The outage of toncenter.com services was fixed. This problem was caused by issue in Cloudflare healthcheck of our infrastructure.
❤3👍1
Cocoon AI smart contract actions are now supported Starting with v1.2.6, the Toncenter Indexer supports the following Cocoon AI smart contract actions along with their decoded message bodies: • cocoon_worker_payout • cocoon_proxy_payout • cocoon_proxy_charge • cocoon_client_top_up • cocoon_register_proxy • cocoon_unregister_proxy • cocoon_client_register • cocoon_client_change_secret_hash • cocoon_client_re…
❤8👍7🤡3🔥2🤩2😁1
Introducing Streaming API V2 The new Streaming API V2 allows you to create an even faster and smoother UX in your products. This innovation is part of the upcoming global “Sub-Second” update of the TON network. Documentation » The deprecation plan for Streaming API V1 will be announced later.
👍8❤2🔥2
Decoded Message Bodies Toncenter API now decodes message bodies using hundreds of known TLB schemes and returns the result in the Message.message_content.decoded field. Previously, only the text_comment type was recognized; the API now supports 800+ TLB schemes. This means responses may include new decoded types and richer structures. Update your parsers to read decoded defensively. If your dApp’s smart contract us…
👍9🔥6❤4🍌2
Overview of New Features in the Toncenter API The first half of this year was dedicated to expanding the Toncenter API with powerful new features that apps and services can leverage to deliver an exceptional user experience. — Actions API The Actions API can detect patterns in sequences of blockchain transactions and return user-friendly data, such as “Exchange 1,000 USDt on DeDust DEX”, “Deposit TON into @stakee s…
❤9🔥6🤝4
Streaming API (Websockets/SSE) is now available for everyone.
👍1
Dear users of toncenter.com/api/index This old version of indexer service is deprecated since December 31, 2024 and will be completely disabled after August 10, 2025. We kindly ask you to migrate to new indexer API v3: toncenter.com/api/v3.
👍1
Streaming API - Websockets/SSE for Enterprise Plan We’re excited to announce that Toncenter has launched a Streaming API! This API enables real-time updates about pending and committed transactions and actions, filtered by specified addresses. The API supports both Server-Sent Events (SSE) and WebSocket protocols, offering flexibility for integration. Currently, the Streaming API is available exclusively to Enterpr…
❤5
New actions supported Tonco.io DEX supported in the Toncenter Actions API: New provider "tonco" added to existing DEX actions: jetton_swap, dex_deposit_liquidity, dex_withdraw_liquidity; tonco_create_pool action added.
🔥5
Get-methods IDs Now, the /accountStates response returns a list of smart contract get method IDs. Based on the presence of certain get methods, you can determine the type of some smart contracts. Adding get method indexing has also improved the accuracy of our Actions API.
❤3
Showing the 12 most recent of 20 posts we hold for @toncenter_news. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 15 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“Toncenter API” (@toncenter_news), 927 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/toncenter_news.
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.