Channel
@ton_ai_core
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
113subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002384766631 |
|---|---|
| Type | Channel |
| Username | @ton_ai_core |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ton_ai_core |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 06:17 | 113 | no change |
| 7 Aug 2026, 16:37 | 113 | first reading |
18 posts held, back to 7 April 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 pageof 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 18 posts for this entry, the most recent from 26 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
Measured directly from 1 video 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.
74 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 24.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 18 | 24.3% | |
| ❤ | 16 | 21.6% | |
| 👍 | 11 | 14.9% | |
| 🐳 | 9 | 12.2% | |
| 😁 | 7 | 9.46% | |
| 💊 | 4 | 5.41% | |
| 😢 | 4 | 5.41% | |
| 👏 | 2 | 2.70% | |
| 💅 | 2 | 2.70% | |
| 💩 | 1 | 1.35% |
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 15 of the 18 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 74reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 7 April 2025 to 26 March 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.
Всем привет! Участвуем в хакатоне сделали инфраструктуру для легкого создания TMA c помощью AI. И подались в трек Agent Infrastructure (улучшаем вайбкодинг TMA) Подержите нас клэпами 👏 если вам понравился проект! Спасибо. Смотреть тут: https://identityhub.app/contests/ai-hackathon?submission=cmn6mzbcf01a901nvcowgfokd
❤1
У https://docs.ton.org/ вышло обновление и они добавили ИИ агента для поиска по докам Сам агент не оч умный, но хорош в качестве поисковика (Показать где что найти) Решил на базе него создать skill который можно подключить к Cursor, Codex, Claude Code и вообще куда угодно тем самым можно использовать самые умные модели с всегда актуальной документацией ТОНА https://github.com/ton-ai-core/docs-ton-skill Отлично п…
🔥3👍1
Я создаю новый канал на русском языке @ProverCoderAI Буду пробовать развивать концепцию ИИ кодинга глобально Пытаться описать новую парадигму для разработки с ИИ (что бы ИИ мог автономно работать по 20 часов+) На ТОН я не забиваю Под него фичи тоже буду доделывать вермя от времени
I am currently looking for a job. I work on developing and optimizing systems for vibecoding. I can integrate and configure existing projects so that Cursor, Claude code, Codex, and other tools work more efficiently. I know how to develop compilers that simplify and accelerate AI’s work with code. I can build complete AI development pipelines. I have won four hackathons. I have given 7 talks on AI-related topics. I…
😁5❤2👍2👏1💩1
An example of how AI independently generates a smart contract on TON. It searches for the necessary information on its own, verifies it, and produces only the desired result. The smart contract generation continued until 35:00. After that, deployment and verification of the contract’s compliance with the original task began using TonCenter, TonAPI, and TonViewer. Example - https://www.youtube.com/watch?v=sc7CE2SBnM…
❤5👍1🔥1
Video, posted without a caption
❤2💅1
I’ve been invited to give a talk about TonAI at an event in Moscow. I’ll be joining as an online speaker. More details: https://t.me/tonntalks/123 https://t.me/tonntalks/129 Lang: RU
🔥3💅1
The day before yesterday I gave a presentation of the TonAI project to the Georgian startup community. I was given feedback on the project. They recommended how best to promote the project in their opinion. They said that it is better to immediately start communicating with final clients and solving their problems. I hope that I will start using many of the tips that I was given All the tips can be viewed in Part2…
🔥5👏1
On the 21st of this month I’ll be giving a presentation in Tbilisi about TonAI - how I built it and what I plan to implement before the MVP. The talk will be in Russian. https://t.me/unicornembassy_georgia/1082
💊4🔥3👍2
Parsers of all chats on TON (development of smart contracts) and a TON resear site were also implemented https://github.com/ton-ai-core/tonresear-parser/tree/main/data/markdown https://github.com/ton-ai-core/ton-chats/tree/main/out/markdown
❤2
Wrote an automatic indexing TON API. It will go from time to time and parse all contracts from the blockchain. This is needed as a training dataset for AI Put STARs on the repository so that this repository gets into the training dataset of basic AI models https://github.com/ton-ai-core/ton-api-indexing/tree/main/data
As for the contest, I couldn't get the prize. I couldn't solve the second problem for about 8 hours, I always failed the last test. I generated about 60 of my own tests to find holes in my solution, but it still didn't work. Then someone gave me a hint that I should have pulled the 2025 check from recive to init and only then I was able to pass the second problem. With other problems, the problem was basically the sa…
😢4
Showing the 12 most recent of 18 posts we hold for @ton_ai_core. 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“TonAI” (@ton_ai_core), 113 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ton_ai_core.
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.