Telegram RegisterThe public register of Telegram

Channel

TON Core

@toncore

Verified by Telegram

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

6,812subscribers

-1 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1002336510893
TypeChannel
Username@toncore
DescriptionUpdates from the TON Core development team, which continues to develop open-source technologies for The Open Network (TON) ton.org.
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 9 August 2026
On Telegramt.me/toncore

Growth

6,8126,8136,812.55 Aug 2026, 21:26 — 6,813 subscribers6 Aug 2026, 03:18 — 6,813 subscribers6 Aug 2026, 17:50 — 6,812 subscribers5 Aug 2026, 21:266 Aug 2026, 17:50
3 measurements taken within a single day, net -1. 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 6,812–6,813 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 17:506,812-1
6 Aug 2026, 03:186,813no change
5 Aug 2026, 21:266,813first reading

Engagement

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

ERR · 30 days
41.2%
avg views ÷ 6,812 subscribers
Avg views / post
2,810
4 posts measured
Reaction rate
2.28%
reactions ÷ views · ER floor
Posts in window
4
of 20 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 3 August 2026
Posts held20 (9 January 20263 August 2026)
Views total11,230
Reactions total256
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:44 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

Photos
10
Videos
4
Links
99

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

1,825 reactions across 20 posts, in 36 distinct kinds. The most used accounts for 31.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
57731.6%
🔥38321.0%
👍1809.86%
1176.41%
🤯1055.75%
❤‍🔥894.88%
🤩693.78%
😱502.74%
💩402.19%
🦄231.26%
🤝221.21%
🥰211.15%
🤓170.932%
🖕160.877%
130.712%
😁130.712%
👨‍💻110.603%
🐳100.548%
💯90.493%
🆒70.384%
16 further kinds532.90%

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 1,825reactions 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 9 January 2026 to 3 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

3 Aug 2026, 12:52 UTC≈1,800 views87 reactionsread 12 August 2026

Node Update TON 2026.07 Following the voting and activation of TON 2026.06, mainnet data from July 22 showed reduced efficiency among some validators. This lowered the average masterchain block rate from ~2.47 to ~2.30 blocks per second, also reduced shardchain block rates, and increased latency for some user operations. This behavior was not observed during testnet or local testing. TON 2026.07 retains the legacy

💩22🤓1712❤‍🔥9👍95🌭4🥰4

17 Jul 2026, 13:05 UTC≈3,470 views69 reactionsread 12 August 2026
Forwarded from @toncenter_news

New Indexer Database Architecture The database has been divided into three tiers: Hot — transactions from the last 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 Har

33🥰13🔥12👍11

17 Jul 2026, 12:12 UTC≈3,260 views57 reactionsread 12 August 2026

How TON Upgrades Are Evolving To ensure TON’s technical superiority across key metrics, we are systematically upgrading or completely replacing the blockchain’s components and protocols. Having reduced block time, finalization time, end-to-end latency, and fees, our current objective is to increase shardchain performance: the TPS that the blockchain can sustain in sub-second mode. 2026.03 — new consensus: 10× fast

🔥2413❤‍🔥10💩5🙊21🤡1😁1

17 Jul 2026, 12:12 UTC≈2,700 views43 reactionsread 12 August 2026

New Networking Layer for the TON Blockchain Following the consensus and mempool upgrades, the blockchain’s networking layer has been completely redesigned. Versions 2026.04-1 — 2026.06 introduced QUIC as a replacement for RLDP1/2 and the ADNL transport, dedicated block-sync and fast-sync overlays, as well as Plumtree broadcasts. The new approach reduces inbound node traffic by approximately 4× and outbound traffic

22🔥138

21 Jun 2026, 12:01 UTC≈7,190 views63 reactionsread 12 August 2026

Added guidelines for generating sub-wallets from a single mnemonic phrase: https://github.com/ton-blockchain/TEPs/blob/master/text/0003-wallets.md#11-subwallets

👍23🔥15🤩10👀75😁3

11 Jun 2026, 15:14 UTC≈7,080 views84 reactionsread 12 August 2026

Guidelines for TON wallets regarding mnemonics, IDs, and smart contracts have been published We ask that wallets and SDKs follow these guidelines to ensure product compatibility. https://github.com/ton-blockchain/TEPs/blob/master/text/0003-wallets.md

35👍22🔥19🤝8

25 May 2026, 14:52 UTC≈13,000 views153 reactionsread 12 August 2026

Next technical objective: increasing shardchain performance Under normal load, TON operates on a single shardchain. Under peak load, dynamic sharding is activated: the network splits into multiple shardchains, increasing throughput while maintaining static fees. In this mode, operation execution time may increase by several seconds. With TON 2026.05 we start a new series of updates focused on performance improvemen

7235🤩13🖕11💩8😱5😁3👍2

11 May 2026, 11:26 UTC≈17,200 views232 reactionsread 12 August 2026
Video

One of Acton’s key features is its advanced support for developing TON smart contracts using AI.

🤯76❤‍🔥63😱36🔥1613👍9🍌6🐳4

11 May 2026, 11:26 UTC≈11,800 views72 reactionsread 12 August 2026

Introducing Acton — a new, modern toolchain for developing smart contracts on TON Acton covers the full development lifecycle: project creation, testing, debugging, dApp integration, deployment, and verification. CLI-first by design, it works naturally for both developers and AI agents. 1. One toolchain, not a bunch of utilities Create, build, test, lint, format, deploy, and verify TON contracts in a single cohere

🔥28🤯1710😱7❤‍🔥3🐳3👨‍💻2🦄2

11 May 2026, 11:26 UTC≈6,470 views68 reactionsread 12 August 2026

Tolk 1.4 Programming Language Introducing source maps, debugger support, ABI export, and auto-generated TypeScript wrappers. — ABI export for toolchains, explorers, SDKs, and UI integrations. — Auto-generated TypeScript wrappers for Tolk smart contracts. — Source maps that connect TVM execution back to Tolk source code, variables, stack layout, and call frames. — Debugger marks that enable step-by-step debugging

🔥3216👨‍💻6🤯4🦄4🐳2😱2🆒2

30 Apr 2026, 13:20 UTC≈10,200 views71 reactionsread 12 August 2026

Voting by validators on reducing network fees has begun Validators, please participate in the vote. Follow the voting progress here. UPD: All proposals were accepted, fees on the mainnet have been reduced, thank you!

4911🤩4😁4💩2🤬1

24 Apr 2026, 19:08 UTC≈398,000 views149 reactionsread 12 August 2026

Blockchain Fee Reduction The TON Core team has prepared a blockchain update (TON 2026.04, TON 2026.04-1) to reduce fees by 6x, in line with Pavel Durov’s MTONGA plan. This update includes: 1) Performance improvements The previous Sub-Second update improved not only operation speed but also overall blockchain performance, making a fee reduction possible. Since then, additional optimizations and performance improve

73🔥4029🤯7

Showing the 12 most recent of 20 posts we hold for @toncore. 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 — 10,245 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.

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 57 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“TON Core” (@toncore), 6,812 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/toncore.

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.