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 12 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 9 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. 16 of the 16 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 132 comparable posts for this entry, running 5 August 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, 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
28 measurements spanning 98 days, net +172. 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 7,524–8,104 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)
Subscribers
Change
12 Nov 2026, 21:10
7,868
-72
8 Nov 2026, 07:50
7,940
-97
5 Nov 2026, 05:45
8,037
+254
2 Nov 2026, 03:15
7,783
-4
30 Oct 2026, 11:05
7,787
+31
27 Oct 2026, 06:18
7,756
-8
24 Oct 2026, 11:50
7,764
+6
21 Oct 2026, 10:16
7,758
+21
18 Oct 2026, 15:09
7,737
-21
15 Oct 2026, 13:06
7,758
+101
12 Oct 2026, 11:01
7,657
+14
5 Oct 2026, 17:19
7,643
-4
28 Sept 2026, 07:14
7,647
+37
18 Sept 2026, 20:55
7,610
-3
14 Sept 2026, 21:41
7,613
+22
11 Sept 2026, 04:18
7,591
-19
6 Sept 2026, 05:57
7,610
-2
2 Sept 2026, 05:22
7,612
+20
30 Aug 2026, 10:16
7,592
-19
27 Aug 2026, 02:38
7,611
first reading
Engagement
330 posts held, back to 5 August 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 46 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
19.1%
avg views ÷ 7,868 subscribers
Avg views / post
1,500
149 posts measured
Reaction rate
0.122%
reactions ÷ views · ER floor
Posts in window
149
of 330 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 25 of 149 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 16 November 2026
Posts held
330 (5 August 2026 – 16 November 2026)
Views total
223,999
Reactions total
48
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 06:12 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
≈7,690
Videos
≈104
Links
≈6,680
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
3m 42s
Average length
56s
Measured directly from 4 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
419 reactions across 81 posts, in 8 distinct kinds. The most used accounts for 50.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
212
50.6%
👍
168
40.1%
🔥
31
7.40%
👏
2
0.477%
😭
2
0.477%
🫡
2
0.477%
💯
1
0.239%
🥰
1
0.239%
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 86 of the 330 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 419 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 330 most recent posts we hold, published 5 August 2026 to 16 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 149 posts held from the last 30 days (2.01%) 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).
Walter Bloomberg 트윗 - TRUMP ON MEETING XI AND PUTIN IN CHINA: WE MAY ALSO MEET WITH KIM JONG UN
#속보
원문 링크 : https://www.twitter.com/DeItaone/status/2122335701677351174
우리의 조사 결과, 오늘 발생한 사건은 특정 트레이더 계정의 유출된 API 키로 인해 발생한 것으로 나타났습니다. Lighter 프로토콜과 스마트 컨트랙트는 영향을 받지 않았습니다.
예방 조치로, 우리는 스마트 컨트랙트에 가디언 모드를 활성화했습니다. 우리의 주요 우선순위는 공격자가 추가 인출을 시도한 관련 자금을 회수하는 것입니다. 이 업그레이드는 Lighter 보안 위원회에 의해 수행될 것입니다.
인출은 일시적으로 중단된 상태를 유지합니다. 현재 목표는 오늘 말까지 컨트랙트 업그레이드를 완료하고 인출을 재개하는 것입니다.
우리는 공격자와 관련된 것으로 의심되는 지갑을 식별했으며, 이는 커뮤니티에서도 플래그가 지정되었습니다:
0xb3fffca23d4444eE73349825ACD84f7b5020e387
https://x.com/ligh…
이건 보니까 라이터에서 MM을 운영하던 지갑의 API Key가 털린 이슈 같네요.
라이터쪽 결함이라기보단,, 개인지갑이슈인거 같습니다
공격방식은 대강 이런듯?
1. API 키탈취
2. API키만으로 출금이불가
3. 그래서 자기가 라이터에 퍼블릭풀 만듬
4. 탈취한 API키로 자기 퍼블릭풀로 그냥 서클 Transfer 해버림
5. 공격자는 트랜스퍼받고 그냥 풀 출금떄려서 돈 빼냄
굳이 따지자면 퍼블릭풀에 그런 공격이 가능했다는게 이슈인거 같은데 이걸 라이터 문제라고 삼기도 애매한거 같아서
그냥 mm의 API 키 탈취가 원인이었던거 같네요
금액은 커보이는데 라이터가 털린건 아니고 라이터 mm 지갑중 하나가 털린거라고 봐야할듯
Q. 타이완은 국가라고 생각하니?
A.
OpenAI: 독자적인 통치 지역임
Gemini: 논쟁있음(= 미정)
Grok : 논쟁있음(= 미정)
Claude: 관점에 따라 다름
DeepSeek: No
Doubao: No
Tongyi Qianwen: No
Yuanbao: No
Kimi: No
👀👀
https://x.com/HE952700/status/2121827037900099686
☺️비트코인 채굴기도 하이재킹 당하는 세상
Ai world 괴상하다 괴상해
https://x.com/wublockchain/status/2121974145588379665
Showing the 12 most recent of 330 posts we hold for @lnsanecoin. 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.
Posts recorded as deleted after publishing
We recorded 1 post on @lnsanecoin as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
8 August 2026
Most recent seen missing
8 August 2026
Median time before seen missing
21 hours
Seen missing in the last 30 days
0
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 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.
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.
New Listings Feed @NewListingsFeed · 59,070 Telegram ranks this channel #9 of 84 here — alongside 83 others — read 23 August 2026
COINNESS News Feed (코인니스) @coinnesskr · 30,320 Telegram ranks this channel #13 of 91 here — alongside 90 others — read 6 September 2026
우리는 트윗충 @twitchoong · 78,934 Telegram ranks this channel #15 of 91 here — alongside 90 others — read 25 August 2026
🔥요블이 세상살이🔥 @yobeullyANN · 22,175 Telegram ranks this channel #24 of 85 here — alongside 84 others — read 21 September 2026
새우잡이어선 공지방 @shrimp_notice · 28,266 Telegram ranks this channel #24 of 93 here — alongside 92 others — read 9 September 2026
기분좋은 마곤 @magonia_b · 25,866 Telegram ranks this channel #25 of 88 here — alongside 87 others — read 11 September 2026
30대에 은퇴번복한 머피 @murphybus · 19,883 Telegram ranks this channel #32 of 88 here — alongside 87 others — read 28 September 2026
졸업준비위원회🎓 @officialunivercityofcrypto · 22,651 Telegram ranks this channel #32 of 86 here — alongside 85 others — read 19 September 2026
Layergg exchange & project alert @layergg · 19,264 Telegram ranks this channel #34 of 91 here — alongside 90 others — read 1 October 2026
코인같이투자 정보 에어드랍🦋 @WeCryptoTogether · 48,075 Telegram ranks this channel #37 of 90 here — alongside 89 others — read 25 August 2026
마샬 공유방 2.0 @marshallog · 21,343 Telegram ranks this channel #39 of 81 here — alongside 80 others — read 22 September 2026
취미생활방📮 @enjoymyhobby · 48,746 Telegram ranks this channel #39 of 92 here — alongside 91 others — read 25 August 2026
DeFi 농부 👨🏻🌾 조선생 @BSC_Farmer_KR · 20,192 Telegram ranks this channel #40 of 88 here — alongside 87 others — read 26 September 2026
코인 갤러리(Coin gallery) @dogeland01 · 20,884 Telegram ranks this channel #40 of 85 here — alongside 84 others — read 24 September 2026
잼민123🦅 @mujammin123 · 25,711 Telegram ranks this channel #41 of 86 here — alongside 85 others — read 13 September 2026
텔레그램 코인 방,채널 - CEN @emperorcoin · 35,428 Telegram ranks this channel #41 of 91 here — alongside 90 others — read 19 August 2026
해달의 투자 정보 공유 @seaotterbtc · 29,986 Telegram ranks this channel #51 of 94 here — alongside 93 others — read 7 September 2026
디지털자산/AI/경제(케이씨지) @coinkcgchannel · 14,330 Telegram ranks this channel #53 of 86 here — alongside 85 others — read 5 October 2026
차분남(차트분석하는남자) @chavoonnam · 21,065 Telegram ranks this channel #53 of 80 here — alongside 79 others — read 24 September 2026
에어드랍ATM @Bounty_ATM · 25,760 Telegram ranks this channel #59 of 79 here — alongside 78 others — read 14 September 2026
변창호 코인사관학교 BCH @BChoSN · 26,321 Telegram ranks this channel #60 of 88 here — alongside 87 others — read 15 September 2026
Gram 🇰🇷 @toncoin_kr · 22,891 Telegram ranks this channel #65 of 88 here — alongside 87 others — read 30 September 2026
신기술은 돈이 된다 공지방 @tlsrltnf · 22,320 Telegram ranks this channel #65 of 86 here — alongside 85 others — read 20 September 2026
폐지줍기 연구소 @airdr0p_lab · 20,423 Telegram ranks this channel #68 of 88 here — alongside 87 others — read 26 September 2026
This channel appears in 27 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 12 November 2026 — this
entry's latest reading, not the date you are reading this.
“인생코인” (@lnsanecoin), 7,868 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/lnsanecoin.
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.