Telegram RegisterThe public register of Telegram
Telegram profile photo for Degen's Club 🍌

Channel

Degen's Club 🍌

@degen_eco

Not marked by Telegram, checked 20 August 2026

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

853subscribers

-120 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002213028722
TypeChannel
Username@degen_eco
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/degen_eco

Topic

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.

Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@deepscan_invesgate8 (8/8 hand-verifiable sample passed)1.00under a minute@deepscan_invesgate (7–1)

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 0 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 15 comparable posts for this entry, running 15 July 2025 to 6 February 2026. 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @deepscan_invesgate. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

8539739137 August 2026 — 973 subscribers7 August 2026 — 972 subscribers8 August 2026 — 972 subscribers16 August 2026 — 969 subscribers24 August 2026 — 900 subscribers31 August 2026 — 903 subscribers10 September 2026 — 906 subscribers19 September 2026 — 900 subscribers3 October 2026 — 887 subscribers13 October 2026 — 875 subscribers19 October 2026 — 871 subscribers25 October 2026 — 867 subscribers1 November 2026 — 865 subscribers8 November 2026 — 860 subscribers17 November 2026 — 853 subscribers7 August 202617 November 2026
15 measurements spanning 102 days, net -120. 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 835–991 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 06:49853-7
8 Nov 2026, 22:16860-5
1 Nov 2026, 05:28865-2
25 Oct 2026, 23:20867-4
19 Oct 2026, 11:30871-4
13 Oct 2026, 11:28875-12
3 Oct 2026, 08:56887-13
19 Sept 2026, 13:19900-6
10 Sept 2026, 03:18906+3
31 Aug 2026, 12:13903+3
24 Aug 2026, 10:36900-69
16 Aug 2026, 01:47969-3
8 Aug 2026, 00:46972no change
7 Aug 2026, 16:01972-1
7 Aug 2026, 13:02973first reading

Engagement

20 posts held, back to 15 July 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 7 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤350.0%
🎉350.0%

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 4 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 6 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 15 July 2025 to 7 February 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.

Recent posts

7 Feb 2026, 08:46 UTC787 views1 reactionsread 8 August 2026

https://x.com/cams_kai/status/2020054282310152603

🎉1

6 Feb 2026, 15:28 UTC920 views2 reactionsread 8 August 2026
Photo

🚨 八部委联合发文虚拟资产监管,不过这次是重大利好。2月6日注定写进中国Crypto RWA监管史 1️⃣ 核心要点一:虚拟货币态度零松动,但RWA被明确切割 $BTC 、 $ETH 、 $USDT 等继续被定性为非法金融活动,境内兑换、交易、ICO、境外服务一律严打,挖矿、广告、公司起名全部封杀。但RWA被单独定义并区别对待,不再一锅端,这是5年来最大的认知升级。 2️⃣ 核心要点二:证监会首次给出RWA权威定义 文件明确现实世界资产代币化 = 用区块链/分布式账本技术,把房产、债券、应收账款等真实资产的所有权/收益权转化为代币,进行发行和交易。 境内RWA原则上禁止,但加了一句关键除外条款——“经业务主管部门依法依规同意,依托特定金融基础设施开展的除外”。 就是想玩RWA?可以,但必须在监管认可的“指定赛道”里玩(比如上海、北上深数据交易所、数人民币基础设施等)。 3️⃣核心要点三:境内资产出海RWA,终于有明确规则了…

❤1🎉1

4 Feb 2026, 14:18 UTC398 views1 reactionsread 8 August 2026
Forwarded from @funfinanceX

🈲 中国再次重申挖矿禁令—— 1)一切虚拟货币挖矿,被定性为非法金融活动; 2)地方政府强化排查与打击; 3)鼓励群众举报,责任直接下沉。 很多人还是没想明白一个问题: 为什么交易能忍,挖矿却始终是红线? 因为交易是零和博弈,再怎么折腾,也只是账户之间的数字变化; 不消耗现实资源,风险最终只在参与者内部结算。 而挖矿是实物——时间——主权的三重穿透。 用现在的电、现在的土地、现在的基础设施,但收益结算的时间和地点都在中国固有体系之外,这是绝对不被允许的。 一定要放弃灰色区域、窗口期这种政治不正确的幻想!

🎉1

31 Jan 2026, 11:18 UTC246 viewsread 8 August 2026
Forwarded from @deepscan_invesgate

🚨 买卖U 我犯法了吗? 简单来说,卖U本身在中国大陆并不直接构成犯罪,但整个交易链条的“怎么卖、卖给谁、资金来源和去向”决定了是否踩到刑事红线。 01/ 中国人民银行等部门反复强调: 1️⃣ 虚拟货币不具有与法定货币等同的法律地位,不具有法偿性,不应且不能作为货币在市场上流通使用。 2️⃣ 虚拟货币相关业务活动属于非法金融活动。 3️⃣ 稳定币被明确纳入虚拟货币范畴,存在被用于洗钱、集资诈骗、违规跨境转移资金等风险。 02/ 最大的雷区:交易对手的资金来源 1️⃣ 如果买家用诈骗款、赌博款、传销款、黑灰产资金来买卖U,你即使不知情,也可能涉嫌掩饰、隐瞒犯罪所得罪或洗钱罪。 2️⃣ “善意第三人”抗辩在实践中很难成立,尤其是大额、频繁交易。 3️⃣ 这是散户/U商最常见被“锤”的原因:收到赃款 → 被冻 → 涉案 → 即使上游不是你干的,你也可能被追责或资金被追缴。 03/ 怎么降低风险? 1️⃣ KYC + 聊天记录(…

13 Jan 2026, 02:10 UTC283 viewsread 8 August 2026
Forwarded from @deepscan_invesgatePhoto

🚨 通俗易懂解释一下币安公告的 #OECD 的 #CARF 1️⃣自动信息交换:参与 CARF 的国家将从加密资产服务提供者处收集本国税务居民的加密资产交易信息,并每年与其他参与国的税务机关进行自动信息交换。 2️⃣ 申报范围:CARF 覆盖范围广泛,不仅包括比特币、以太坊等加密货币,还包括稳定币、非同质化代币(NFT)以及以加密资产形式存在的衍生品等。 3️⃣ 申报信息内容:用户身份信息(姓名、地址、居住国、纳税人识别号(TIN)等)和交易信息(交易类型、累计交易金额、交易次数等详细交易数据) 4️⃣申报义务主体:凡是为客户或代表客户从事加密资产交易撮合、提供交易平台或相关服务的加密资产服务提供者,均负有申报义务。包括交易所、做市商、加密资产运营主体 5️⃣ 防范跨境逃税:CARF 有助于防止通过加密资产交易产生的所得逃税行为。通过信息自动交换机制,各国税务机关能够掌握跨境加密资产交易情况。 6️⃣ 监管要求加强:…

8 Jan 2026, 12:26 UTC205 viewsread 8 August 2026
Forwarded from @deepscan_invesgateFile

此前,中国刑法学研究会、上海高院指导,上海二中院与中国人民大学法学院联合主办刑事审判研讨会,第四期聚焦「涉虚拟货币犯罪案件的适法统一」主题,研讨内容整理如下: 1️⃣ 涉虚拟货币洗钱犯罪中「主观明知」的认定,应综合判断涉虚拟货币洗钱罪中的主观明知,以防止客观归罪。 2️⃣ 涉虚拟货币洗钱犯罪的行为类型及既遂标准的认定,一是准确把握「掩饰、隐瞒犯罪所得及其收益的来源和性质」这一犯罪本质;二是实施洗钱犯罪构成要件所规定的掩饰、隐瞒犯罪所得及其收益行为,即属于犯罪既遂;三是依法从严打击洗钱犯罪,坚决维护国家金融安全。 3️⃣ 涉虚拟货币非法经营犯罪的认定,如行为不具有经营行为特征,仅属于个人持币、炒币,则一般不认定为非法经营罪。但如果其明知他人非法买卖或者变相买卖外汇,仍通过兑换虚拟货币方式提供帮助,情节严重的,应认定为非法经营罪的共犯。

8 Jan 2026, 03:09 UTC174 viewsread 8 August 2026
Forwarded from @deepscan_invesgatePhoto

虚拟货币“U商”陷阱 1️⃣ 买卖 USDT 本身并不当然构成洗钱罪,单纯进行虚拟货币交易通常不会直接被认定为洗钱。 2️⃣ 但现实中仍存在严重刑事风险,包括涉嫌帮助信息网络犯罪活动罪、掩饰隐瞒犯罪所得罪,情节严重的甚至可能构成非法经营罪。 3️⃣ 司法关注的核心并不是你是否“想犯罪”,而是资金来源是否清晰,大额交易、来历不明资金,以及明知或应知异常仍协助转移,都会成为定罪关键。 4️⃣ 做场外交易一定要做 KYC,一定要验证U的来源是否涉及非法。 如果涉及非法那很有可能变成帮信罪、掩隐罪、非法经营罪 交流群 | 非法地址免费查询

7 Jan 2026, 02:19 UTC157 viewsread 8 August 2026
Forwarded from @deepscan_invesgate

目前国内政策是个人持有或交易加密货币(如 $BTC 等“炒币”)以及非盈利目的的日常换取 $USDT 本身并不直接构成违法行为,但相关活动需严格遵守外汇管制、反洗钱等规定。 真正的风险主要在于资金/U的来源、出入金方式以及是否涉及盈利或大额交易,如果来源非法或绕过监管,可能触及刑事责任(如非法经营罪或掩饰、隐瞒犯罪所得罪)。 ✅ 个人持有/交易加密货币不违法,但风险自担:国内未明确禁止个人持有虚拟货币,其被视为虚拟财产,具有一定财产价值。政策重点打击的是机构化交易、ICO、矿场等“相关业务活动”,而非个人行为。 ✅ 非盈利目的日常换U不违法:小额、非营利性的USDT兑换(如个人跨境支付或持有)未被定为违法,但需确保不涉及外汇管制违规。 🚨 主要风险: 1️⃣ U的来源非法:如果U来自电诈、网赌、洗钱等犯罪资金,交易方可能不知情但仍被追责(如“善意取得”不适用虚拟货币)。 推荐免费查询非法U工具:@DeepScanPro_b…

5 Jan 2026, 13:31 UTC153 viewsread 8 August 2026
Forwarded from @deepscan_invesgatePhoto

目前在多个 EVM 链 上,似乎有 数百个钱包正在被持续盗取资金,每个受害钱包被盗金额较小(单个受害者合计低于 2,000 美元),且 根本原因尚未查明。 截至目前,累计被盗金额约为 107,000 美元,且 盗窃总额仍在持续上升中。 可疑地址: 0xAc2e5153170278e24667a580baEa056ad8Bf9bFB 交流群 | 非法地址分析工具

3 Jan 2026, 01:52 UTC266 viewsread 8 August 2026

📌 TZAdsCArx2cU3C79i8tvudSGhkJRZFqHKy 💰 余额:28.61 USDT ⛓ 主链:USDT-TRC20 ├ ⻛控评级:风险高,请谨慎 ├ ⾮法关联事件:疑似恶意地址 ├ ⾮法交易总额:$ 0 ‼ ⾮法交易详情: ├ 涉及与非法活动实体交易:Guarantee Merchant ├ 涉及额度:$ 0.00 └ 交易路径:直接交易-中转 1 次 🧬 与你交易过的⾮法地址: ├ TDuYf6t4f3ZGXSDcEgqLwfUwXEZqbaeh7T (Suspected malicious address, Laundering, Guarantee Merchant) └ 交易记录 1 | 交易记录 2 | 交易记录 3 ├ TW5RX79CU6ArUTePvCZHnwCykyoDQrAD3V (Suspected malicious address, Laund…

Showing the 12 most recent of 20 posts we hold for @degen_eco. 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.

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.

Mentions

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.

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.

TG/TON Community(华语)
@tgtoncn · 43,528
Telegram ranks this channel #1 of 72 here — alongside 71 others — read 27 August 2026
ME News
@MetaEraNews · 17,913
Telegram ranks this channel #4 of 66 here — alongside 65 others — read 27 September 2026
Toncoin 中文频道
@toncoin_cn · 135,900
Telegram ranks this channel #6 of 87 here — alongside 86 others — read 17 August 2026
欧易OKX公告
@OKXAnnouncements_CN · 45,120
Telegram ranks this channel #28 of 88 here — alongside 87 others — read 28 August 2026
TechFlow 深潮 | 加密货币&区块链新闻
@TechFlowDaily · 18,874
Telegram ranks this channel #34 of 91 here — alongside 90 others — read 5 October 2026
PANews Web3丨加密货币丨区块链新闻频道
@ChannelPANews · 23,620
Telegram ranks this channel #40 of 96 here — alongside 95 others — read 17 September 2026
OUTA Announcement
@outa_announcement · 25,692
Telegram ranks this channel #44 of 81 here — alongside 80 others — read 10 September 2026
BlockBeats
@theblockbeats · 38,249
Telegram ranks this channel #46 of 92 here — alongside 91 others — read 1 September 2026
Odaily资讯速递
@Odaily_News · 19,493
Telegram ranks this channel #53 of 93 here — alongside 92 others — read 26 September 2026
PixelSwap
@PixelSwap_io · 457,875
Telegram ranks this channel #68 of 85 here — alongside 84 others — read 27 August 2026
jump.fun
@JumpDotFun · 93,405
Telegram ranks this channel #74 of 90 here — alongside 89 others — read 17 August 2026
大宇投资频道
@BTCdayu2 · 29,380
Telegram ranks this channel #75 of 85 here — alongside 84 others — read 8 September 2026
Investment kingyru 💎 EN
@investkingyru_en · 18,954
Telegram ranks this channel #79 of 80 here — alongside 79 others — read 30 September 2026
DeJob—Web3招聘求职频道📮
@DeJob_official · 48,023
Telegram ranks this channel #81 of 94 here — alongside 93 others — read 27 August 2026

This channel appears in 14 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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“Degen's Club 🍌” (@degen_eco), 853 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/degen_eco.

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.