The official announcements channel for SubQuery.
Our open and inclusive community channel is https://t.me/subquerynetworkcommunity
https://linktr.ee/subquerynetwork
Created
Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.
Growth
27 measurements spanning 95 days, net -665. 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 8,726–9,591 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)
Subscribers
Change
9 Nov 2026, 19:01
8,826
-37
6 Nov 2026, 05:59
8,863
-25
3 Nov 2026, 12:00
8,888
-17
31 Oct 2026, 05:08
8,905
-12
28 Oct 2026, 12:57
8,917
-11
25 Oct 2026, 21:28
8,928
-27
22 Oct 2026, 11:18
8,955
-23
19 Oct 2026, 05:57
8,978
-22
15 Oct 2026, 20:44
9,000
-10
12 Oct 2026, 23:47
9,010
-40
6 Oct 2026, 09:59
9,050
-49
29 Sept 2026, 08:21
9,099
-58
18 Sept 2026, 21:41
9,157
-28
14 Sept 2026, 12:19
9,185
-20
11 Sept 2026, 03:56
9,205
-35
6 Sept 2026, 15:00
9,240
-32
2 Sept 2026, 05:13
9,272
-19
30 Aug 2026, 11:13
9,291
-25
27 Aug 2026, 06:58
9,316
-21
23 Aug 2026, 21:18
9,337
first reading
Engagement
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 51 pages of 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.
What this channel posts
Photos
487
Videos
106
Links
825
Lifetime counters from Telegram’s own channel header, read 12 November 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.
Video runtime
10s
Average length
10s
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.
Reaction mix
1,582 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 17.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
283
17.9%
🎉
262
16.6%
🤩
250
15.8%
🔥
244
15.4%
👏
226
14.3%
🥰
221
14.0%
😱
88
5.56%
🙏
4
0.253%
🤯
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,582 reactions 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
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…
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…
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.
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
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…
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…
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
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.
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.
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.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Futureverse ($ROOT) @futureverse_meta · 20,318 Telegram ranks this channel #6 of 70 here — alongside 69 others — read 2 September 2026
Portal to Bitcoin Announcements @portaltobitcoin_announcements · 82,845 Telegram ranks this channel #9 of 88 here — alongside 87 others — read 1 September 2026
peaq @peaqnetwork · 40,904 Telegram ranks this channel #9 of 94 here — alongside 93 others — read 28 August 2026
Casper Official Announcements @casperofficialann · 33,865 Telegram ranks this channel #14 of 81 here — alongside 80 others — read 1 September 2026
Morph Layer Announcement @MorphL2announcement · 583,839 Telegram ranks this channel #18 of 92 here — alongside 91 others — read 25 August 2026
MultiversX - Announcements @MultiversXAnn · 269,081 Telegram ranks this channel #20 of 87 here — alongside 86 others — read 15 August 2026
📣 Vinu News @Vinu_News · 133,325 Telegram ranks this channel #25 of 88 here — alongside 87 others — read 15 August 2026
Port3 Announcement @port3network · 38,095 Telegram ranks this channel #29 of 84 here — alongside 83 others — read 29 August 2026
Quai Network Announcements @QuaiNetwork_Announcements · 20,866 Telegram ranks this channel #32 of 84 here — alongside 83 others — read 21 September 2026
AlloX Announcements @alloxdotai · 38,757 Telegram ranks this channel #37 of 70 here — alongside 69 others — read 26 September 2026
Gopher Announcements📢 @gopherannouncements · 42,326 Telegram ranks this channel #49 of 92 here — alongside 91 others — read 27 August 2026
Script Network Announcements @scriptnetworkann · 29,527 Telegram ranks this channel #51 of 86 here — alongside 85 others — read 6 September 2026
Self Chain @selfchainxyz · 99,166 Telegram ranks this channel #51 of 91 here — alongside 90 others — read 14 August 2026
CVALPHA_NEWS @CVALPHA_news · 52,342 Telegram ranks this channel #54 of 94 here — alongside 93 others — read 22 August 2026
Engines of Fury Announcements @EnginesOfFuryNews · 57,538 Telegram ranks this channel #55 of 89 here — alongside 88 others — read 22 August 2026
This channel appears in 15 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“SubQuery Announcements (Official)” (@subquerynetwork), 8,826 subscribers as measured 9 November 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.