Telegram RegisterThe public register of Telegram

Channel

Quack AI Announcement

@QuackAIAnn

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

218,816subscribers

-1,014 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002433402631
TypeChannel
Username@QuackAIAnn
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 live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/QuackAIAnn

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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

218,816219,830219,3236 August 2026 — 219,830 subscribers6 August 2026 — 219,781 subscribers7 August 2026 — 219,649 subscribers8 August 2026 — 219,520 subscribers10 August 2026 — 219,307 subscribers10 August 2026 — 219,199 subscribers11 August 2026 — 219,109 subscribers12 August 2026 — 218,816 subscribers6 August 202612 August 2026
8 measurements spanning 7 days, net -1,014. 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 218,664–219,982 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:13218,816-293
11 Aug 2026, 19:43219,109-90
10 Aug 2026, 22:26219,199-108
10 Aug 2026, 00:30219,307-213
8 Aug 2026, 21:22219,520-129
7 Aug 2026, 20:21219,649-132
6 Aug 2026, 18:00219,781-49
6 Aug 2026, 00:54219,830first reading

Engagement

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

ERR · 30 days
0.496%
avg views ÷ 218,816 subscribers
Avg views / post
1,080
12 posts measured
Reaction rate
0.484%
reactions ÷ views · ER floor
Posts in window
12
of 21 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 12 August 2026
Posts held21 (3 July 202612 August 2026)
Views total13,014
Reactions total63
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 17:58 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

Video runtime
7m 10s
Average length
29s

Measured directly from 15 videos 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.

Reaction mix

136 reactions across 21 posts, in 3 distinct kinds. The most used accounts for 77.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10577.2%
👍2014.7%
🔥118.09%

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 136reactions 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 3 July 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 21 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @QuackAIAnn. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 21 most recent posts we hold for this entry, published 3 July 2026 to 12 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

12 Aug 2026, 03:42 UTC292 views2 reactionsread 12 August 2026
Video

📊 Month-End Treasury Overview with Q402 You let an agent spend. Now it is month end. Q402 keeps the books: a treasury overview by chain and vendor, total paid to any single vendor with its recurring cadence, and a per agent spend report against each wallet's caps. All read only. npx -y @quackai/q402-mcp 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

2

3 Aug 2026, 12:22 UTC934 views3 reactionsread 12 August 2026
Photo

🧠 FAT Brings an Economic Body to AI Agents FAT gives AI agents an economic body. Governance gives them a nervous system. @MossAI_Official's Fungible Agent Token standard is the missing interface for tokenizing autonomous agent economies — and maps cleanly to how AI-governed DAOs already operate. Excited for what ships next. 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

3

31 Jul 2026, 11:43 UTC≈1,120 views2 reactionsread 12 August 2026
Video

📍 Q402 MCP Seoul Meetup Q402 MCP Seoul Meetup starts this Monday, August 3 AI agents are no longer just answering questions. They are starting to hold wallets, request payments, settle invoices, and move stablecoins on-chain. At the meetup, we’ll show how Q402 MCP works inside Claude, Codex, Cursor, and other AI clients: 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

1🔥1

31 Jul 2026, 11:04 UTC975 views2 reactionsread 12 August 2026
Video

📍 Q402 MCP Seoul Meetup — August 3 Q402 MCP Seoul Meetup starts this Sunday, August 3. AI agents are no longer just answering questions. They are starting to hold wallets, request payments, settle invoices, and move stablecoins on-chain. At the meetup, we’ll show how Q402 MCP works inside Claude, Codex, Cursor, and other AI clients: 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

2

30 Jul 2026, 10:23 UTC972 views1 reactionsread 12 August 2026
Video

🔐 Q402 Signing Key Options Where your agent's signing key lives is a design choice. Q402 gives three modes: 🔸 your EOA signs locally 🔸 an exported Agent Wallet key signs in-process 🔸 a server-custodied wallet signs on Q402's side 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

1

28 Jul 2026, 10:23 UTC≈1,000 views8 reactionsread 12 August 2026
Video

👛 Give Your Agent a Wallet Give 👏 Your 👏 Agent 👏 A 👏 Wallet 👏 It pays. It stays under the limits you set. It never touches gas. Agent Q runs on Q402. Gasless stablecoin rails, live on 12 chains. 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

8

27 Jul 2026, 10:22 UTC931 views6 reactionsread 12 August 2026
Photo

🚀 One-click Q402 install in Cursor Q402 now installs into Cursor @cursor_ai in one click, via http://cursor.directory. One signed request from your agent triggers a gasless stablecoin payment (USDC, USDT, RLUSD, USDG), settled on-chain across 12 EVM chains. No approve, transfer, pay steps. No separate gas. npx -y @quackai/q402-mcp 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

6

24 Jul 2026, 10:22 UTC≈1,180 views5 reactionsread 12 August 2026
Photo

🇰🇷 Quack AI lands in Seoul Quack AI is landing in Seoul. Your AI agent is about to make its first onchain payment. Bring Codex, connect Q402, and your AI agent sends a real payment on Avalanche. 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

5

21 Jul 2026, 11:06 UTC≈1,330 views10 reactionsread 12 August 2026
Video

⚡ Payments integration in one line Wiring an agent into payments used to be a week of work: an SDK, API keys, config. With Q402 it's one line in your MCP config. npx -y @quackai/q402-mcp 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

🔥10

20 Jul 2026, 14:23 UTC≈1,260 views8 reactionsread 12 August 2026
Video

🚀 Gasless stablecoin rails for AI agents Every agent payment still runs on rails built for humans. Gas fees. Approval popups. Manual invoices. So we rewrote them. Gasless stablecoin rails for AI agents. Live on 12 chains, 200K+ settlements, under a second. npm i @quackai/q402-mcp 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

5👍3

16 Jul 2026, 14:23 UTC≈1,580 views9 reactionsread 12 August 2026
Video

🎬 Blocked Before It Hit the Chain This payment never happened. An agent tried to spend past its cap. Q402's policy hooks stopped it before authorization. Nothing was signed. Nothing touched the chain. Enforcement before authorization. Settlement on-chain. 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕Medium | ⚙️Gitbook

5👍4

14 Jul 2026, 13:43 UTC≈1,440 views7 reactionsread 12 August 2026
Video

🚆 AI Agent Spending Controls, Enforced by Contract Every major player is building payment rails for AI agents. The rails are becoming free. The hard problem was never moving the money. It's making sure your agent spends it the way you intended. Spend caps. Allowlists. Enforced by contract, not by promise. 230,000+ gasless agent payments on @BNBCHAIN and counting. 📱Twitter | 📱Channel | 💬Chat | 🌎Website | 🌐APP | 📕M

7

Showing the 12 most recent of 21 posts we hold for @QuackAIAnn. 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 — 167,524 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

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.

Mentions

Named by 2 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.

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

“Quack AI Announcement” (@QuackAIAnn), 218,816 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/QuackAIAnn.

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.