Channel
@XDAG_Community
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
437subscribers
+70 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001888859405 |
|---|---|
| Type | Channel |
| Username | @XDAG_Community |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/XDAG_Community |
Crypto & trading — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 |
|---|---|---|
| 6 Oct 2026, 22:37 | 437 | +1 |
| 26 Sept 2026, 21:58 | 436 | +10 |
| 14 Sept 2026, 15:19 | 426 | +4 |
| 7 Sept 2026, 05:21 | 422 | +24 |
| 30 Aug 2026, 05:12 | 398 | +11 |
| 23 Aug 2026, 12:28 | 387 | +11 |
| 16 Aug 2026, 06:58 | 376 | +9 |
| 8 Aug 2026, 06:30 | 367 | no change |
| 8 Aug 2026, 00:17 | 367 | first reading |
20 posts held, back to 1 December 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 3 August 2026. An engagement rate over an empty window would be a number about nothing.
72 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 68.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 49 | 68.1% | |
| 👍 | 12 | 16.7% | |
| 🔥 | 6 | 8.33% | |
| 👏 | 4 | 5.56% | |
| 👎 | 1 | 1.39% |
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 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 72 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 1 December 2025 to 3 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.
XDAG Community Developer Regular Meeting Minutes (52nd) On August 1, 2026, the XDAG community developers held their 52nd regular meeting, where participants discussed and arranged community work: I. Technical Issues 1. Prepare for the third halving on the mainnet around the 24th of this month; 2. Continue researching the XDAG P2P protocol code II. Participants: Daniel, Messi, LucasMLK, FamousL, Vibes XDAG commun…
🔥3
Minutes of the XDAG Community Developer Meeting (51st) On June 27, 2026, XDAG community developers held their 51st regular meeting, where participants discussed and arranged community work: I. Technical Seminars 1. In-depth discussion of future XDAG development models for sustainable iterative upgrades based on AI; 2. Discuss the implementation path for XDAG version 1.0; 3. The community team is reviewing the XDAG …
👍5❤2
Minutes of the XDAG Community Developers Meeting (50th) On June 3, 2026, the XDAG community developers held their 50th regular meeting, where participants discussed and arranged community work: I. Technical Seminars 1. Initiate preliminary work for the official version of XDAG V1.0. V1.0 will be the most important upgrade in XDAG's history. The mainnet will have the ability to abolish the whitelist threshold requir…
❤7
For the attention of community members, We need to improve the liquidity of the MEXC exchange. MEXC's liquidity standards: - Total value of XDAG held by users on MEXC must ≥ 50000 USDT - Average daily spread below 2% - Combined buy & sell depth within a 2% price spread > 1,000 USDT - Non-self traded volume > 5,000 USDT P.S: Improvements must be completed within 30 days, or will be delisted. ———————————————— 请社区爱好者…
XDAG mainnet has been upgraded to V0.8.3 to fix some bugs. So far, everything is running normally. ———————————————— XDAG主网已升级至V0.8.3，修复已发现的问题。截至目前，运行正常。
❤3
After the mainnet is upgraded and runs smoothly for a period of time. We are pleased to announce the successful completion of V0.8.1 upgrade.🎉🎉🎉 ———————————————— 在主网节点升级并平稳运行了一段时间后，我们开心的宣布，主网0.8.1版本升级顺利完成!🎉🎉🎉
👏3
Please wait our mainnet upgrade complete.
❤3
XDAG Community pinned «XDAG V0.8.1 Mainnet Upgrade Announcement The community has recently completed the V0.8.1 public beta and is now preparing for the mainnet upgrade. The relevant work arrangements are as follows: Ⅰ Upgrade Arrangement Start Time: April 10th, 12:00 (UTC) …»
With the efforts of the community members, we passed the assessment of MEXC. Please continue to maintain liquidity. ———————————————— 经过社区成员的努力，我们通过了MEXC本次考核，已经恢复正常交易区。 请大家务必保持平台流动性。
❤3👍2
XDAG V0.8.1 Mainnet Upgrade Announcement The community has recently completed the V0.8.1 public beta and is now preparing for the mainnet upgrade. The relevant work arrangements are as follows: Ⅰ Upgrade Arrangement Start Time: April 10th, 12:00 (UTC) End Time: Subject to official announcement Snapshot Data: April 10th, 2026, 12:00 (UTC) Upgrade Content: 1. Support for variable transaction fees and sorting 2.…
❤3👏1
XDAG Community Developers Meeting Minutes (49th) On March 28, 2026, XDAG community developers held their 49th regular meeting, where participants discussed and arranged community work: I. Technical Progress 1. Start the V0.8.1 community beta; 2. Discuss the precautions for the V0.8.1 mainnet upgrade, which mainly involves variable fees and node data loading bug fixes II. Community matters 1. Complete technical sup…
❤7👎1
XDAG Version 0.8.1 Public Test Announcement Dear community members, XDAG version 0.8.1 has been prepared and is now officially open for the community public beta, and I hope you will actively participate in this public beta. The public beta arrangement is as follows: I. General information Deadline: 12:00, 2 April (UTC) Version: XDAG V0.8.1 Testnet Browser: https://testexplorer.xdag.io/ II. Participation Methods 1…
👍4
Showing the 12 most recent of 20 posts we hold for @XDAG_Community. 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.
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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“XDAG Community” (@XDAG_Community), 437 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/XDAG_Community.
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.