Channel
@subquerynetwork
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,425subscribers
-66 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001314954022 |
|---|---|
| Type | Channel |
| Username | @subquerynetwork |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/subquerynetwork |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 04:15 | 9,425 | -30 |
| 10 Aug 2026, 06:13 | 9,455 | -33 |
| 7 Aug 2026, 13:45 | 9,488 | -3 |
| 6 Aug 2026, 23:15 | 9,491 | no change |
| 6 Aug 2026, 23:04 | 9,491 | first reading |
18 posts held, back to 4 March 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 14 pagesof 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 19 May 2026. An engagement rate over an empty window would be a number about nothing.
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.
1,578 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 17.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 281 | 17.8% | |
| 🎉 | 262 | 16.6% | |
| 🤩 | 250 | 15.8% | |
| 🔥 | 244 | 15.5% | |
| 👏 | 225 | 14.3% | |
| 🥰 | 221 | 14.0% | |
| 😱 | 88 | 5.58% | |
| 🙏 | 3 | 0.19% | |
| 🤯 | 3 | 0.19% | |
| ⚡ | 1 | 0.063% |
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 18 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 1,578reactions 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 4 March 2026 to 19 May 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.
Big news for the SubQuery community. We're winding down the decentralized network to focus fully on AskSubQuery - our AI platform for exploring blockchain data in plain language. SQT remains at the center. Full details + your next steps 👇 https://bit.ly/4eU4aqr
❤4🙏3
Signed Brittany Seales
We have just integrated GoldRush (powered by Covalent)as a data source on AskSubQuery. This means users can now query GoldRush’s datasets using natural language. No APIs. No complex queries. No setup. Just ask. From wallet activity to token balances and cross-chain insights, AskSubQuery handles the complexity behind the scenes - translating questions into structured queries and returning clear answers in real time…
🎉7
Signed Brittany Seales
Nobody brags about their indexer. Until it goes down. Then suddenly it’s the most important piece of the stack.
🔥4
Signed Brittany Seales
We asked three AI assistants a simple on-chain question: “What are the top 5 tokens on Uniswap by Token Value Locked?” ChatGPT is guessing ❌ Claude doesn’t know ❌ AskSubQuery just answers ✅ The responses tell a bigger story about the current state of AI + blockchain data. • ChatGPT produced a confident, but incorrect, answer • Claude couldn’t access the data it needed • AskSubQuery returned the correct result ins…
❤1🤯1
Signed Brittany Seales
Update: All affected users have now been fully compensated. The recovery process is complete. Thanks to the community for your patience while we worked through this.
❤25🎉21🔥20👏17🤩15🥰12😱2
Signed Brittany Seales
We’ve published our full post-mortem on the recent security incident. The investigation identified an additional exploit, bringing the total impacted to 359,614,732 SQT. No private keys were compromised. Fixes are live, and all affected users will be fully compensated. Full details + recovery plan ↓ https://bit.ly/4syDr5M
🎉30👏20🤩18🥰18❤15🔥14
Signed Brittany Seales
We are continuing to investigate the recent exploit. For transparency, the primary attack transaction can be viewed here: https://basescan.org/tx/0xf23efa0fab0f6b8c0790d48c6a07abc472ceb32fb3c1b4618b967c09c15a07bf The staking contract has been impacted, and withdrawals will not be successful at this time. Functionality will be restored once the contract is fully refunded. We want to reiterate that all affected user…
😱36❤24👏23🔥19🥰16🎉13🤩7
Signed Brittany Seales
A vulnerability in one of our contracts has been exploited. An immediate fix has been deployed, and the team is actively investigating other potential points of compromise. A total of 129,364,800 SQT was affected. We want to assure the community that all victims will be compensated in full. We are closely monitoring the situation and will provide further updates as more information becomes available. Thank you for…
😱50❤23🔥19🤩19🥰17👏15🎉14🤯1
Signed Brittany Seales
How do you manage smart contract permissions across 30+ chains.. without running any backend? OpenZeppelin does it with a fully client-side app. Behind the scenes, 30+ indexers on the SubQuery Network provide the data layer. Here’s how it works 👇 https://bit.ly/4dSWog3
🤩27❤19🔥17🎉16🥰16👏11🤯1
Signed Brittany Seales
Hunt eggs, not data 🐰 We’ll handle the indexing. Happy Easter to all those who celebrate.
🎉20❤18🤩18🥰15👏13🔥13
Signed Brittany Seales
SubQuery is now live on TRON. Developers can now index TRON smart contracts using familiar Ethereum tooling via EVM-compatible RPCs. No new stack required. Build TRON dApps with the same powerful SubQuery SDK you already know. More chains. Same seamless experience.
🔥25👏22❤20🎉13🥰13🤩11
Signed Brittany Seales
You see the UI. You see the token price. You see the dashboards. You don’t see the indexing layer making it all possible. That’s where we live.
❤25🎉23🔥21🥰17👏13🤩12
Signed Brittany Seales
Showing the 12 most recent of 18 posts we hold for @subquerynetwork. 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 — 628,042 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 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“SubQuery Announcements (Official)” (@subquerynetwork), 9,425 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/subquerynetwork.
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.