Channel
@ai_dev_wall
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,204subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003856221521 |
|---|---|
| Type | Channel |
| Username | @ai_dev_wall |
| Created | Between 1 February 2026 and 15 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/ai_dev_wall |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:33 | 1,204 | -5 |
| 9 Aug 2026, 16:02 | 1,209 | +1 |
| 6 Aug 2026, 17:20 | 1,208 | -2 |
| 6 Aug 2026, 08:47 | 1,210 | no change |
| 6 Aug 2026, 00:48 | 1,210 | first reading |
20 posts held, back to 15 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 3 August 2026 |
|---|---|
| Posts held | 20 (15 April 2026 – 3 August 2026) |
| Views total | 88 |
| Reactions total | 18 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 08:47 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.
🧠 The 2026 International Olympiad in Artificial Intelligence starts today. As a token of support for those who will reinvent our civilization, we'll issue 🏆 240 exclusive Intelligence Cups to the winners. 💵 We guarantee minimum buyback prices ($1,000 per Gold Cup, etc.), but the cups' limited supply may make them worth much more on the secondary market. Good luck, AI coders! 🍀
Signed ʀᴇꜱɪꜱᴛᴏʀ ₁₃₁₂.ₜₒₙ
⭐️ Hoton-MCP is Live You can now purchase Telegram Stars, Premium and top-up your Telegram Gram balance from your AI Agent — just ask, and it does for you in seconds. 🔗 Connect hoton-mcp to any AI that supports MCP (OpenClaw, Hermes, Claude, Cursor, Codex, etc), then talk to it in any simple language, for example: ⭐️ Buy 100 Stars for @damx 🎁 Gift @monk 3 months of Premium 💎 Top up @crow with 5 GRAM It works out …
Signed ʀᴇꜱɪꜱᴛᴏʀ ₁₃₁₂.ₜₒₙ
Teleton Agent v0.9.0 is here. New Cocoon provider. Fully redesigned WebUI. Smarter tool discovery. Per-tool access control. Latest AI models, many fixes and more. Learn more about 0.9.0: t.me/TeletonAgents/54 Run your own agent: telegra.ph/Deploy-Your-Teleton-Agent-03-03 GitHub: github.com/TONresistor/teleton-agent/ Install / Update now: npm install -g teleton@latest
Signed ʀᴇꜱɪꜱᴛᴏʀ ₁₃₁₂.ₜₒₙ
We won the TON AI Agent Hackathon and turned the project into a live marketplace — ctlx.cc. You deploy your agent, it earns per call in TON / USDT. Payments and escrow are handled for you. There's a skill that rolls out your agent (or product) onto the site in a few minutes. Or you can run agents/products on our machine using @ctlx_seller_bot Doesn't have to be an agent. We sell subscriptions and access too — Claud…
Signed John Doe
A quick update on the topic of the channel: in the major update to dTON’s liteservers, we’ve added MCP. You can now type Add dton.io/mcp in Claude / Codex, log in via Telegram, and the agent will be able to work with liteservers itself: view balance, rates, keys, select an SDK for Go/Python/Node, check the liteserver, and view analytics on RPS, methods and duration. Our LiteServer features: • Pay as you go, $0.02 …
Signed Andrey Tvorozhkov
Hey Folks 🫡 I’m selling project . If you’re interested DM me
Signed Denis S
Hi, can anyone share projects building agent economies on TON? I'm interested in A2A solutions. I know the marketplace ctlx.cc that took part in a hackathon, but so far it looks like an Agent-to-Human solution.
Signed Tand
Hey everyone 👋 I just published a small package I've been working on - ton-better-auth. It's a Better Auth plugin that lets users sign in with their TON wallet using TON Connect. The idea came from needing this for a project and not finding a clean solution. It handles the ton_proof verification on the backend - replay protection, signature validation, state-init parsing for different wallet versions, all that stuff…
Signed MonoBit
🛠 Developing for TON just became 10x faster. The new toolchain makes smart contracts easy to create, test, and deploy. Most importantly, fully AI-ready. It replaces TON’s fragmented tooling stack with one developer flow. Start building!
Signed 𝘴𝘱𝘦𝘯𝘥 $
One of Acton’s key features is its advanced support for developing TON smart contracts using AI.
Signed ʀᴇꜱɪꜱᴛᴏʀ ₁₃₁₂.ₜₒₙ
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…
Signed ʀᴇꜱɪꜱᴛᴏʀ ₁₃₁₂.ₜₒₙ
GM everyone ❤️ I built a Cocoon client in Go, It follows the same wire protocol and contracts interface as the existing C++ client. It’s cross-platform, with a simple standalone CLI. I named it Gocoon. It is ideal if you want to connect to Cocoon locally without going through third-party entities, and for your AI agents and LLMs-powered mini-apps. In the video above, another of my projects (TON Browser) in which I…
Signed ʀᴇꜱɪꜱᴛᴏʀ ₁₃₁₂.ₜₒₙ
Showing the 12 most recent of 20 posts we hold for @ai_dev_wall. 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 — 148,370 of 1,169,250entries 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.
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 4 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.
@ai_dev_wall named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“AI Dev Wall” (@ai_dev_wall), 1,204 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ai_dev_wall.
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.