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 10 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 12 other registered channels. 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.
Matching posts — open both and compare (6 of the pairs behind the counts below)
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
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. 12 of the 12 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 159 comparable posts for this entry, running 30 July 2026 to 16 November 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).
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 17 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.
Growth
67 measurements spanning 103 days, net -513. 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 16,247–16,914 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)
Subscribers
Change
16 Nov 2026, 18:09
16,324
-22
13 Nov 2026, 09:11
16,346
-24
10 Nov 2026, 22:46
16,370
-17
9 Nov 2026, 08:11
16,387
-8
7 Nov 2026, 23:50
16,395
-16
6 Nov 2026, 22:46
16,411
-17
6 Nov 2026, 01:06
16,428
-1
5 Nov 2026, 02:16
16,429
-11
4 Nov 2026, 03:30
16,440
-1
3 Nov 2026, 03:47
16,441
-2
2 Nov 2026, 05:20
16,443
-3
1 Nov 2026, 01:38
16,446
-4
31 Oct 2026, 04:30
16,450
-10
30 Oct 2026, 02:09
16,460
-14
29 Oct 2026, 03:37
16,474
-12
28 Oct 2026, 00:30
16,486
-7
27 Oct 2026, 03:06
16,493
-16
26 Oct 2026, 04:01
16,509
-4
25 Oct 2026, 03:08
16,513
-5
24 Oct 2026, 05:27
16,518
first reading
Engagement
253 posts held, back to 30 July 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 83 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.86%
avg views ÷ 16,324 subscribers
Avg views / post
467
116 posts measured
Reaction rate
0.567%
reactions ÷ views · ER floor
Posts in window
116
of 253 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 110 of 116 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 17 November 2026
Posts held
253 (30 July 2026 – 17 November 2026)
Views total
54,188
Reactions total
290
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 06:46 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈21,500
Videos
≈340
Links
≈18,800
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
2m 26s
Average length
24s
Measured directly from 6 videos 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
584 reactions across 237 posts, in 10 distinct kinds. The most used accounts for 47.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
276
47.3%
❤
173
29.6%
🔥
64
11.0%
🤔
21
3.60%
😁
14
2.40%
😱
13
2.23%
🤬
13
2.23%
👏
7
1.20%
😢
2
0.342%
🎉
1
0.171%
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 239 of the 253 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 587 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 253 most recent posts we hold, published 30 July 2026 to 17 November 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
Telegram’s own ‘edited’ marker: 3 of 116 posts held from the last 30 days (2.59%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
젠슨 황, X 계정 소개 수정…엔비디아 관련 로고와 'CEO' 직함 삭제
PANews 11월 17일 소식에 따르면, 엔비디아 전 CEO 젠슨 황이 X 플랫폼 계정의 개인 소개를 수정하여 'CEO'라는 직함을 삭제했으며, 현재는 '엔비디아 창립자'만 표기하고 있다. 또한 계정 홈페이지에 원래 있던 엔비디아 회사 관련 로고도 철거되었다.
🔗 https://www.panewslab.com/ko/articles/01a1e758-796d-7631-ac5b-53c5d3a7c4f7
한국시간 다가오는 새벽2시
☑️워시 연준의장 연설 예정
이번 연설은 FOMC 금리 결정 발표가 아니라 개회사입니다. 따라서 금리 관련 직접적인 발언이 없을 수도 있음.
다만 다음 세 가지가 언급되는지 주목할 필요가 있음.
인플레이션: 물가 상승 압력에 대한 평가
금리 전망: 추가 긴축 또는 완화 가능성
고용·생산성: AI와 생산성 향상이 경제에 미치는 영향
특히 금리 인상 가능성을 강조하면 BTC 등 위험자산에 부담이 될 수 있으니 참고!
#워시 #연준의장
이건 보니까 라이터에서 MM을 운영하던 지갑의 API Key가 털린 이슈 같네요.
라이터쪽 결함이라기보단,, 개인지갑이슈인거 같습니다
공격방식은 대강 이런듯?
1. API 키탈취
2. API키만으로 출금이불가
3. 그래서 자기가 라이터에 퍼블릭풀 만듬
4. 탈취한 API키로 자기 퍼블릭풀로 그냥 서클 Transfer 해버림
5. 공격자는 트랜스퍼받고 그냥 풀 출금떄려서 돈 빼냄
굳이 따지자면 퍼블릭풀에 그런 공격이 가능했다는게 이슈인거 같은데 이걸 라이터 문제라고 삼기도 애매한거 같아서
그냥 mm의 API 키 탈취가 원인이었던거 같네요
금액은 커보이는데 라이터가 털린건 아니고 라이터 mm 지갑중 하나가 털린거라고 봐야할듯
["라이터서 익스플로잇 발생 의혹 제기"...LIT 급락]
블록체인 분석업체 MLM온체인이 "라이터(LIT)에서 익스플로잇이 발생한 것으로 보인다. 100% 확실하진 않다"고 텔레그램 채널을 통해 전했다. 해당 소식 이후 LIT는 바이낸스 USDT 무기한 선물 마켓 기준 20% 넘게 급락, 현재는 2.35 달러 근처에서 거래되고 있다.
https://coinness.com/news/1175721
✔️Anthropic IPO, Kraken·Gate·Bitget 3곳 비교
Anthropic IPO 공개 청약을 진행하는 3개 거래소의 조건을 비교해 봤습니다.
① Kraken — 토큰화 주식 (ANTx)
• 청약 수수료: 5% (스프레드)
• 청약 마감: 11월 19일 02:00 (한국시간)
• 실제 주식이 아닌 1:1 연동 토큰
• 상장 후 24시간 거래 가능
• 미배정 금액 환불, 마감 전 취소 가능
② Gate — 실제 미국 주식 (ANT)
• 청약 수수료: 5만 USDT 이하 5%, 초과분 10%
• 청약 마감: 11월 17일 18:00 (한국시간)
• 3곳 중 유일하게 실제 주식 지급
• 청약 금액 비례 배정, 락업 없음
• 미배정 금액 환불, 청약 금액은 중도 출금 불가
③ Bitget — 토큰화 자산 (rANT)
• 청약…
[토스, 코인지갑 출시…이더·테더·USDC 주고받는다]
모바일 금융 플랫폼 토스를 운영하는 비바리퍼블리카가 토스 앱에서 USDT(테더)와 USDC(써클)을 비롯한 달러 스테이블코인과 이더리움(ETH)을 주고받을 수 있는 가상자산 지갑서비스 ‘토스 코인지갑’을 선보인다고 이데일리가 전했다. 토스 가입자라면 별도의 신청이나 자격 제한 없이 누구나 이용할 수 있으며 토스 앱 홈 화면의 자산 카테고리에서 지갑을 생성할 수 있다.
https://coinness.com/news/1175675
원문 보기 : https://www.edaily.co.kr/News/Read?newsId=02027046645646376&mediaCodeNo=257&utm_source=naver&utm_medium=referral&utm_campaign=news_syndicati…
젠슨황, CEO 복귀 논의
https://www.bloomberg.com/news/articles/2026-11-15/huang-discusses-comeback-as-nvidia-chief-with-allies-ft-says?utm_source=website&utm_medium=share&utm_campaign=copy
비트코인 하락 원인들 정리
1. 앤트로픽 IPO 발 유동성 쏠림 현상
- 스페이스X 이후, 역대 최대를 갱신할 것으로 예상되는 앤트로픽 때문에 자금이 몰리는 현상이 발생
실제로 요번주 내내 코인베이스 BTC 순매도가 큰 규모로 나오는 중
- 실제로 스페이스X 때에도 IPO 이전에 하락이 나타났고, IPO 100일 후에 전고점을 탈환했다는 주장
2. 바이낸스 청산 유도설
- 바이낸스와 외부 고래들이 유동성이 부족한 시간에 지지선을 무너뜨려 연쇄 청산을 일으켰다는 주장
3. 블랙먼데이를 미리 반영
- 젠슨황과 엔비디아 순환금융 의심 여파 발 블랙먼데이를 미리 반영했다는 주장
지식을 외우는 능력이 쓸모없어졌다기보다는 지식을 꺼내올 수 있다는 사실만으로는 본인이 더 이상 전문가임을 증명하기 어려워진 세상이 된듯.
단순히 안경을 벗기는게 아니라 막지 못하면 차라리 전부 안경 씌우고 시험의 방식을 바꾸는게 맞지 않을까 싶음. 문제를 푸는 비용도 저렴해졌지만 문제를 채점하고 평가하는 비용도 매우 저렴해졌다고 생각함
최근 AI를 이해한 채용 시장에서는 다양한 해법이나 제안이 나오는데 (카파시 / 앤트로픽 / 쇼피파이 / 알트먼 / 이션 몰릭)
정리해보면 무엇을 찾아야하는지, 가져온 답이 맞는지, 상황에 적용해 책임을 질 수 있는지까지 체크할 수 있는 시험 방법을 찾아보는게 더 발전적인 방향이 아닐까
Showing the 12 most recent of 253 posts we hold for @centurywhale. 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 8 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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@centurywhale named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@capy_onchain named in 1 post, 13 November 2026 – 13 November 2026
@dreykon_xyz named in 1 post, 13 November 2026 – 13 November 2026
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.
에어드랍코리아 (Airdropkorea) @airdrop_kor · 21,207 Telegram ranks this channel #9 of 84 here — alongside 83 others — read 24 September 2026
COINNESS News Feed (코인니스) @coinnesskr · 30,320 Telegram ranks this channel #21 of 91 here — alongside 90 others — read 6 September 2026
불개미 CRYPTO @fireant_crypto · 32,684 Telegram ranks this channel #28 of 92 here — alongside 91 others — read 4 September 2026
DeFi 농부 👨🏻🌾 조선생 @BSC_Farmer_KR · 20,192 Telegram ranks this channel #29 of 88 here — alongside 87 others — read 26 September 2026
🔥요블이 세상살이🔥 @yobeullyANN · 22,175 Telegram ranks this channel #29 of 85 here — alongside 84 others — read 21 September 2026
신기술은 돈이 된다 공지방 @tlsrltnf · 22,320 Telegram ranks this channel #30 of 86 here — alongside 85 others — read 20 September 2026
폐지줍기 연구소 @airdr0p_lab · 20,423 Telegram ranks this channel #32 of 88 here — alongside 87 others — read 26 September 2026
잼민123🦅 @mujammin123 · 25,711 Telegram ranks this channel #32 of 86 here — alongside 85 others — read 13 September 2026
에어드랍ATM @Bounty_ATM · 25,760 Telegram ranks this channel #37 of 79 here — alongside 78 others — read 14 September 2026
마샬 공유방 2.0 @marshallog · 21,343 Telegram ranks this channel #38 of 81 here — alongside 80 others — read 22 September 2026
졸업준비위원회🎓 @officialunivercityofcrypto · 22,651 Telegram ranks this channel #38 of 86 here — alongside 85 others — read 19 September 2026
코인같이투자 정보 에어드랍🦋 @WeCryptoTogether · 48,075 Telegram ranks this channel #38 of 90 here — alongside 89 others — read 25 August 2026
기분좋은 마곤 @magonia_b · 25,866 Telegram ranks this channel #43 of 88 here — alongside 87 others — read 11 September 2026
ZAP Tech News @zaponblast · 62,737 Telegram ranks this channel #46 of 82 here — alongside 81 others — read 21 August 2026
텔레그램 코인 방,채널 - CEN @emperorcoin · 35,428 Telegram ranks this channel #51 of 91 here — alongside 90 others — read 19 August 2026
JackToken Announcements @jacktokencom · 376,000 Telegram ranks this channel #53 of 65 here — alongside 64 others — read 8 September 2026
30대에 은퇴번복한 머피 @murphybus · 19,883 Telegram ranks this channel #54 of 88 here — alongside 87 others — read 28 September 2026
Gram 🇰🇷 @toncoin_kr · 22,891 Telegram ranks this channel #55 of 88 here — alongside 87 others — read 30 September 2026
천지일보 독자알림창 @cheonjiilbo · 19,674 Telegram ranks this channel #57 of 65 here — alongside 64 others — read 30 September 2026
변창호 코인사관학교 BCH @BChoSN · 26,320 Telegram ranks this channel #72 of 88 here — alongside 87 others — read 15 September 2026
해달의 투자 정보 공유 @seaotterbtc · 29,986 Telegram ranks this channel #73 of 94 here — alongside 93 others — read 7 September 2026
코인 갤러리(Coin gallery) @dogeland01 · 20,884 Telegram ranks this channel #83 of 85 here — alongside 84 others — read 24 September 2026
새우잡이어선 공지방 @shrimp_notice · 28,266 Telegram ranks this channel #83 of 93 here — alongside 92 others — read 9 September 2026
취미생활방📮 @enjoymyhobby · 48,746 Telegram ranks this channel #83 of 92 here — alongside 91 others — read 25 August 2026
This channel appears in 24 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 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“코인맵핵 🎈” (@centurywhale), 16,324 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/centurywhale.
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.