Channel
@w3_cn
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
805subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001791141810 |
|---|---|
| Type | Channel |
| Username | @w3_cn |
| Created | Between 1 December 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 | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/w3_cn |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @pego_ecological_data_cn | 8 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 5 September 2024 to 29 January 2025. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @w3_cn — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 15:20 | 805 | no change |
| 7 Aug 2026, 08:47 | 805 | first reading |
20 posts held, back to 5 September 2024 — 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 20 posts for this entry, the most recent from 29 January 2025. An engagement rate over an empty window would be a number about nothing.
101 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 94.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 95 | 94.1% | |
| 🎉 | 3 | 2.97% | |
| 👏 | 2 | 1.98% | |
| ❤ | 1 | 0.99% |
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 17 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 101reactions 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 5 September 2024 to 29 January 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.
值得相守的PEGO社区人，大家新年快乐！ 回顾来时的一年，由于一些不可抗力因素所带来的影响，我们选择在此期间沉寂。 但是为了同一个愿景，我们不会放弃。 基金会将于2025年3月20日正式公布全新发展规划，属于PG的时代不会丢失，只是早一天到来或者晚一天到来！ 届时PEGO将会迎来全新的社区发展模式，创新技术的植入，以及再次的人声鼎沸，希望届时你和我顶峰相见！
👍17🎉3👏2
关于 Mythic Echo IDO结束的公告 由于本次IDO规模过小， Mythic Echo运营团队决定将参与本次IDO的USDT在72小时内原路返回，原运营计划将会暂停推动，推动OSKDAO新的方案，将会根据社区现状进行重新设计，并于近期公布。
👍1
OSKDAO滑点调整提案 由于原OSKDAO滑点调整提案，持有VT用户没有在正式投票之前进入钱包授权，无法成功投票，现重新发起关于OSKDAO的滑点调整提案，请查看详情并根据您自己的判断做出投票。 注意: 持有VT钱包的用户必须在快照于区块: 9455821之前进行一次钱包授权才能真正参与道治理投票。 DAO治理社区关于OSKDAO滑点的新提案内容如下： PG/OSKDAO交易滑点改为10%，USDT/OSKDAO滑点改为0，ME/OSKDAO滑点改为0，OSKDAO-IDO地址改为0 https://www.snapoll.net/0xef20df52b625d451eb6f009ec1034ddcd17c735d/proposals/4%7C0xef20df52b625d451eb6f009ec1034ddcd17c735d
PEGO公链 OSKDAO | Mythic Echo 攜手PEGO與 OSKDAO 共建鏈遊新紀元 【专属主题】 OSKDAO | Mythic Echo启动发布 即OSKDAO赋能应用说明 金牌主持:主持：Shirley 主讲说明:技术社区代表 Lilian ⏰会议时间：2024/11/29 19:30-21:00 (GMT+08:00) 中国标准时间 - 北京 点击链接入会，或添加至会议列表： https://meeting.tencent.com/dm/iNAu0vBFg2sV #腾讯会议：395-948-987 今天目睹一场前所未有的伟大革命正在悄然兴起，这不是一场简单的变革，而是一场触及心灵、重塑公链的格局和辉煌，让我们携手并进，共同书写PEGO&OSKDAO新篇章。 大家敬请关注以下频道: Website：https://www.myt…
OSKDAO滑点调整提案 由于原OSKDAO滑点调整提案部分合约地址录入错误，现重新发起关于OSKDAO的滑点调整提案并对原提案进行替换，请查看详情并根据您自己的判断做出投票。 DAO治理社区关于OSKDAO滑点的新提案内容如下： PG/OSKDAO交易滑点改为10%，USDT/OSKDAO滑点改为0，ME/OSKDAO滑点改为0，OSKDAO-IDO地址改为0 https://www.snapoll.net/0xef20df52b625d451eb6f009ec1034ddcd17c735d/proposals/4%7C0xef20df52b625d451eb6f009ec1034ddcd17c735d
PEGO公链 OSKDAO | Mythic Echo 攜手PEGO與 OSKDAO 共建鏈遊新紀元 【专属主题】 OSKDAO | Mythic Echo启动发布 即OSKDAO赋能应用说明 金牌主持：Shirley 主讲说明:技术社区代表 Erics ⏰会议时间：2024/11/28 20:05-22:00 (GMT+08:00) 中国标准时间 - 北京 点击链接入会，或添加至会议列表： https://meeting.tencent.com/dm/iNAu0vBFg2sV #腾讯会议：607-543-031 今天目睹一场前所未有的伟大革命正在悄然兴起，这不是一场简单的变革，而是一场触及心灵、重塑公链的格局和辉煌，让我们携手并进，共同书写PEGO&OSKDAO新篇章。 大家敬请关注以下频道: Website：https://www.mythice…
👍1
《OSKDAO | Mythic Echo》攜手 Pego Network 與 OSKDAO，共建鏈遊新紀元 我們很高興正式宣布，《OSKDAO | Mythic Echo》（ME），一款基於北歐神話背景的革命性鏈遊，將與 Pego Network 和 OSKDAO 深度合作，開啟 GameFi 與去中心化生態的新篇章！ 什麼是《OSKDAO | Mythic Echo》？ 《OSKDAO | Mythic Echo》是一款結合 快節奏卡牌策略對戰 和 Web3 技術優勢 的創新鏈遊。它汲取了傳統卡牌遊戲的精華，同時突破現有鏈遊的局限，將策略、博弈、技能與金融價值完美融合，帶來前所未有的沉浸式體驗。 1.北歐神話背景：玩家將與雷神、洛基、奧丁等傳奇角色並肩作戰，進入一個充滿策略與挑戰的神話世界。 2.獨特玩法：SNAP 博弈、隨機戰鬥區域、技能與卡牌的自由組合，讓每場遊戲都獨一無二。 3.NFTfi 創新：遊戲中的 N…
👍9
📣ONEBOND跨链桥Tron-PEGO流动性建设完成通知 亲爱的PEGO用户： 我们诚挚地通知您，ONEBOND跨链桥现已全面完成Tron与PEGO网络之间的USDT💎跨链流动性建设💎。 您现在可以顺畅使用ONEBOND跨链桥，将TRON资产无缝跨链至PEGO。请注意，为确保PEGO生态使用的流畅和安全，跨链后用户需进行OB-USDT到W3-USDT的转换操作。 📍重要操作步骤： 1️⃣跨链至PEGO网络后，前往以下转换页面完成OB-USDT至W3-USDT的兑换操作：https://usdt.w3swap.org/#/ 2️⃣合约地址： OB-USDT: 0xE169260BCFdCc37b0a72f4788bc1A918EF8e9933 W3-USDT: 0x02F9Bebf5E54968D8Cc2562356C91ECDE135801B 我们感谢您对PEGO和ONEBOND跨链服务的支持。如有任何疑问，请随…
👍9
📣PEGO用户公告：ONEBOND跨链桥支持PEGO对Tron的USDT跨链功能 亲爱的PEGO用户： 我们很高兴地通知您，ONEBOND现已支持PG对Tron的跨链功能。此次跨链服务采用流动性解决方案，以提升交易效率和用户体验。当前跨链功能已经开放，但由于流动性建设尚在进行中，请等待流动性完成建设后进行正式使用。 我们预计在未来15天内完成流动性建设。届时，我们将向大家发送正式通知，以便您能顺畅地使用跨链服务。 🌐Onebond跨链桥官方地址： https://www.onebond.io/ 感谢您对我们的支持与理解！ PEGO生态基金会 2024年11月2日
👍5❤1
📣关于推进PEGO社区去中心化管理的公告 亲爱的PEGO社区成员： 为进一步推动DAO（去中心化自治组织）机制的落地，真正实现社区的去中心化治理，赋予社区成员更大的自主权，我们将对现有的管理结构进行调整，以增强社区共识和自治权。 具体变更如下： 1️⃣正式退役现有公共群组：所有原有的官方公共群组将停止运营。此举意在去除中心化管理的束缚，使社区治理结构更加开放，赋予每位社区成员更多参与和发声的机会。 2️⃣保留PEGO生态数据公示平台、PEGO中英、W3生态中英等5个频道：PEGO生态将继续对数据进行透明化披露，确保信息公开与透明。频道将用于发布PEGO生态的关键运营数据及紧急事项，帮助所有成员实时掌握生态动态。频道链接如下： ▪️PEGO News： https://t.me/PEGO_NEWS ▪️PEGO中文频道： https://t.me/PEGO_cn ▪️W3生态频道： https://t.me/w3_cn…
👍5
Photo, posted without a caption
👍4
🎉全新里程碑！ PEGO链上交易量突破🏆11,500,000！ 见证沉淀和积累的力量
👍6
Showing the 12 most recent of 20 posts we hold for @w3_cn. 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 — 833,544 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@w3_cn named 1 handle 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“W3生态频道” (@w3_cn), 805 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/w3_cn.
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.