Channel
@cheqd_announcements
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
737subscribers
-13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001518157992 |
|---|---|
| Type | Channel |
| Username | @cheqd_announcements |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/cheqd_announcements |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 20:58 | 737 | -4 |
| 5 Sept 2026, 19:41 | 741 | -4 |
| 21 Aug 2026, 22:08 | 745 | -3 |
| 15 Aug 2026, 16:17 | 748 | -2 |
| 7 Aug 2026, 02:16 | 750 | no change |
| 7 Aug 2026, 02:03 | 750 | first reading |
20 posts held, back to 29 October 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 page 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 20 posts for this entry, the most recent from 17 June 2026. An engagement rate over an empty window would be a number about nothing.
245 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 46.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 115 | 46.9% | |
| ❤ | 66 | 26.9% | |
| 👏 | 36 | 14.7% | |
| 👍 | 26 | 10.6% | |
| 🎉 | 1 | 0.408% | |
| 👎 | 1 | 0.408% |
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 19 of the 20 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 245 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 29 October 2025 to 17 June 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.
👋 Hi cheqmates, We're inviting the community to join a discussion on a potential future change to network inflation, specifically the possibility of reducing inflation to 0%. This topic is quite important with both potential benefits and trade-offs. Any such change could impact validator incentives, staking dynamics, and the broader economics of the network, which is why community input is important. Please join t…
👏9👍2❤1
Following on from our partnership announcement with Vouched, we’ve published a deeper look at what we’re building together and how it works under the hood. At its core, this is about building trust in AI agents in a way that is decentralised, verifiable, and independently auditable. Instead of relying on a single platform to define or control trust, the system is anchored to open standards and uses cryptographic id…
👍10🔥6👏1
🔥️️️️️️ We’re pleased to announce our partnership with Vouched 🔥️️️️️️ Vouched KYA now integrates the cheqd network, adding cryptographic agent identities, verifiable credentials and tamper-proof audit trails, without vendor lock-in. 📰 Read more here
🔥14👏5
🤝 Community Update 🤝 We're happy to share that the cheqd Telegram and Discord channels will remain open and are not being paused. Going forward, the channels will be community managed, led by Luke, Matt, and the current ambassadors. Thank you to everyone who made it clear how important these channels are to the community, and for making your voices heard. Let's continue supporting each other and pushing cheqd and …
❤13👏3🎉1🔥1
⚠️ Important Wallet Update for the cheqd Community ⚠️ Leap Wallet has officially announced it will sunset their wallet on 28 May 2026. Users are encouraged to migrate to an alternative wallet before the deadline. To help make the transition simple, we’ve created a step-by-step guide to move from Leap Wallet to Keplr Wallet. 📘 Read the migration guide here. Reminder: Your assets remain on-chain. Never share your s…
To all community members, node operators, and technical partners, As shared during our latest AMA, the cheqd network is in a strong and stable position. Solid foundations are in place, supported by key partner agreements that enable the delivery of compliant and interoperable decentralised identity solutions. To maintain this position, we have reviewed our strategy and resources, initiating internal changes across …
👍4❤1👎1
We’re pleased to announce that cheqd is now integrated into the Talao wallet, one of Europe’s leading Self-Sovereign Identity (SSI) wallets. Users can now access cheqd’s infrastructure directly within Talao, strengthening a shared commitment to open, interoperable decentralised identity. Talao is deeply embedded in the European Digital Identity (EUDI) ecosystem, and this collaboration reflects a clear focus on alig…
❤20🔥6
We are pleased to share that our partner Anonyome Labs has announced a pilot programme with Utah Valley University. This initiative enables students to test secure digital versions of their student IDs and academic credentials in a mobile wallet environment, all running on a production DID on mainnet. This collaboration underscores cheqd's role in enabling secure, scalable solutions for verifiable credentials. Rea…
🔥20
🇪🇺Under-16s offline? How Europe’s push could bring decentralised ID into the picture Europe is seriously considering restricting social media access for under-16s, driven by growing concern about minors’ mental health and online safety. The question is how these rules would actually be enforced in practice. As calls for stricter age limits grow louder, platforms are under pressure to prove compliance. But doing so …
👍4❤3
It’s the Yearly Wrap Up Time!🔥 🆔Product & Protocol Updates 🧑🤝🧑Partnerships & Alliances 🚀Accelerator Programmes 🧠Verifiable AI Hackathon 🗳️Community & Governance 🏆Market Recognition 🌎Events & Conferences 💡Media, Thought Leadership & Education 🍷Looking Ahead to 2026 🆔Product & Protocol Updates🆔 This year marked a major step forward with the launch of cheqd’s MCP-enabled Agentic Trust solution. Alongside this, mul…
🔥11👏5
European Business Wallets — New Proposal to Accelerate EU’s Digital Future Last month, the European Commission unveiled a proposal that could fundamentally change how companies operate across the Single Market: European Business Wallets. Designed as a core component of the EU’s Digital Public Infrastructure, the initiative aims to simplify cross-border operations, reduce administrative burden, and strengthen the com…
🔥4❤3
💡Our Q4 Product Update is now live🔥 Q4 2025 was a focused quarter for the cheqd team, centred on improving quality, stability, and enterprise readiness across the stack. We shipped upgrades across cheqd Studio, SDKs, the block explorer, and the core network, bringing the platform into a strong, production-ready position heading into 2026. 🧠Key highlights include revocation and status management in cheqd Studio, wit…
🔥10❤1
Showing the 12 most recent of 20 posts we hold for @cheqd_announcements. 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.
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 1 registered channel — 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.
@cheqd_announcements named 7 handles 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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“cheqd Announcements” (@cheqd_announcements), 737 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/cheqd_announcements.
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.