2 measurements spanning 4 days. 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 65–67 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 01:45
66
no change
6 Aug 2026, 00:48
66
first reading
Engagement
8 posts held, back to 24 June 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 8 posts for this entry, the most recent from 31 July 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
1
Links
4
Lifetime counters from Telegram’s own channel header, read 10 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
127 reactions across 6 posts, in 13 distinct kinds. The most used accounts for 41.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
53
41.7%
❤🔥
20
15.7%
👏
15
11.8%
❤
6
4.72%
🍾
6
4.72%
🆒
5
3.94%
🏆
5
3.94%
🐳
5
3.94%
👍
5
3.94%
🥰
3
2.36%
🙏
2
1.57%
⚡
1
0.787%
😍
1
0.787%
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 6 of the 8 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 127reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 24 June 2025 to 31 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
NEW ARTICLE: Why AI in Crypto
We just published our vision of how AI agents are revolutionizing the blockchain space!
What's inside:
👉The declarative programming revolution - how AI is changing how developers build
👉Solving the blockchain UX crisis - making DeFi accessible to everyone
👉Real-world case study featuring Pupas Protocol's AI-powered staking
Key insights:
🔶AI agents are transforming crypto from complex …
🚀 MAJOR MILESTONE ACHIEVED: $50K TVL! 🚀
We just crossed the $50,000 Total Value Locked mark! 📈
This is HUGE for our AI-powered DeFAI protocol! Our intelligent agents have been working around the clock to optimize yields and grow our community's investments.
💪 Community Power:
Massive thanks to our early supporters who believed in AI-powered yield farming! You're the real MVPs building the future of intelligent DeFi…
Pupas AI pinned «PUPAS PROTOCOL ROADMAP 2025-2026 RELEASED We're shaping the next evolution of AI-powered DeFAI on Waves blockchain. Our comprehensive strategic roadmap outlines 5 core priorities through 2026: PRIORITY 1: Pool Ecosystem Expansion (Q3 2025) ▪ USDT Exchange…»
⚡ YESTERDAY'S PERFORMANCE REPORT
While most DeFi protocols delivered single-digit returns, Pupas Protocol's AI agent captured 75.62% APY on July 4th.
THE NUMBERS:
Peak daily APY: 75.62%
Current live APY: 14.06%
WHY AUTOMATED MANAGEMENT WINS:
✅ AI operates 24/7 - never sleeps, never misses opportunities
✅ Instant strategy pivots based on market conditions
✅ Zero emotional trading - pure data-driven decisions
✅ Captu…
💭 CONCEPT: Multi-Asset Strategy
Hey Pupas community,
We're exploring an interesting idea for the protocol's future.
🔍 THE CONCEPT
What if our AI agent could use your staked USDT as collateral to access other tokens and optimize yields across multiple assets?
Currently we focus on USDT lending/staking, but this could unlock broader opportunities across Waves DeFi.
⚠️ EARLY STAGE
This is purely conceptual right now. …
🚀 PUPAS PROTOCOL IS LIVE
The first AI-powered USDT staking protocol on Waves blockchain!
━━━━━━━━━━━━━━━━━━━━━━━━━━
⚡ WHAT WE'VE BUILT
Autonomous AI agents that analyze DeFi protocols 24/7, finding and executing optimal yield strategies for your USDT. No manual management. No fixed returns. Just intelligent automation.
🎯 HOW IT WORKS
Stake USDT → Get LP Tokens → AI Invests → Hourly Price Updates → Withdraw Any…
Showing the 8 most recent of 8 posts we hold for @pupasprotocol. 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 — 508,057 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.
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.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“Pupas AI” (@pupasprotocol), 66 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/pupasprotocol.
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.