Telegram RegisterThe public register of Telegram
Telegram profile photo for TON Core

Channel

TON Core

@toncore

Verified by Telegram

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

6,912subscribers

+99 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
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 live25 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/toncore

Topic

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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.

Growth

6,8126,9126,8625 August 2026 — 6,813 subscribers6 August 2026 — 6,813 subscribers6 August 2026 — 6,812 subscribers13 August 2026 — 6,835 subscribers19 August 2026 — 6,836 subscribers22 August 2026 — 6,838 subscribers25 August 2026 — 6,848 subscribers28 August 2026 — 6,847 subscribers31 August 2026 — 6,842 subscribers3 September 2026 — 6,848 subscribers9 September 2026 — 6,847 subscribers12 September 2026 — 6,840 subscribers17 September 2026 — 6,862 subscribers25 September 2026 — 6,912 subscribers5 August 202625 September 2026
14 measurements spanning 51 days, net +99. 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,797–6,927 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 14:156,912+50
17 Sept 2026, 07:596,862+22
12 Sept 2026, 23:406,840-7
9 Sept 2026, 08:416,847-1
3 Sept 2026, 21:386,848+6
31 Aug 2026, 13:536,842-5
28 Aug 2026, 05:266,847-1
25 Aug 2026, 10:376,848+10
22 Aug 2026, 13:066,838+2
19 Aug 2026, 13:536,836+1
13 Aug 2026, 01:146,835+23
6 Aug 2026, 17:506,812-1
6 Aug 2026, 03:186,813no change
5 Aug 2026, 21:266,813first reading

Engagement

21 posts held, back to 9 January 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 12 pages 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 21 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1,933 reactions across 21 posts, in 36 distinct kinds. The most used accounts for 30.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤59330.7%
🔥43122.3%
👍19810.2%
⚡1176.05%
🤯1055.43%
❤‍🔥894.60%
🤩693.57%
😱502.59%
💩482.48%
🤓271.40%
🤝231.19%
🦄231.19%
🥰211.09%
🖕160.828%
✍130.673%
😁130.673%
👨‍💻110.569%
🐳100.517%
💯90.466%
🆒70.362%
16 further kinds603.10%

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

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

12 Aug 2026, 14:14 UTC≈4,610 views96 reactionsread 20 August 2026

Node Update TON 2026.08 Following the deployment of TON 2026.07 on August 4, the block production rate and other network metrics returned to their normal levels. The next update, TON 2026.08, will activate collators on TON mainnet. Currently, validators both assemble blocks from user transactions and validate them. After the update, these responsibilities will be separated. Dedicated collator nodes will assemble b…

🔥44👍16❤12🤓9💩8🤡5🍾1😭1

3 Aug 2026, 12:52 UTC≈3,090 views89 reactionsread 20 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🤓18❤13❤‍🔥9👍9⚡5🌭4🥰4

17 Jul 2026, 13:05 UTC≈4,420 views69 reactionsread 20 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,960 views58 reactionsread 20 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…

🔥25❤13❤‍🔥10💩5🙊2⚡1🤡1😁1

17 Jul 2026, 12:12 UTC≈3,120 views43 reactionsread 20 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🔥13⚡8

21 Jun 2026, 12:01 UTC≈7,490 views63 reactionsread 20 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👀7❤5😁3

11 Jun 2026, 15:14 UTC≈7,320 views84 reactionsread 20 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,400 views153 reactionsread 20 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…

❤72⚡35🤩13🖕11💩8😱5😁3👍2

11 May 2026, 11:26 UTC≈17,400 views232 reactionsread 20 August 2026
Video

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

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

11 May 2026, 11:26 UTC≈12,000 views72 reactionsread 20 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🤯17❤10😱7❤‍🔥3🐳3👨‍💻2🦄2

11 May 2026, 11:26 UTC≈6,600 views68 reactionsread 20 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…

🔥32❤16👨‍💻6🤯4🦄4🐳2😱2🆒2

30 Apr 2026, 13:20 UTC≈10,300 views71 reactionsread 20 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!

❤49✍11🤩4😁4💩2🤬1

Showing the 12 most recent of 21 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.

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

“TON Core” (@toncore), 6,912 subscribers as measured 25 September 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.