Channel
@lastmoneyalpha
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
22,971subscribers
-130 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001678418089 |
|---|---|
| Type | Channel |
| Username | @lastmoneyalpha |
| Description | Web3·TCG·AI, 기회가 모이는 막돈방. 정보는 빠르게, 혜택은 확실하게. 막돈방 : t.me/lastmoneyalpha 막돈방채팅 : t.me/lastmoneychat 문의 : @lastmoney64 / @edtls123 / @stalim17 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/lastmoneyalpha |
Gaming — 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 88% 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.
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 in near-verbatim form 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @GemHive/3748026 Aug 2026, 11:20 UTC | @lastmoneyalpha/10417 · this entry26 Aug 2026, 23:42 UTC | 1.00 | 12 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @GemHive | 7 (7/7 hand-verifiable sample passed) | 1.00 | 2.5 hours | @GemHive (5–2) |
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 209 comparable posts for this entry, running 6 August 2026 to 13 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.
Recorded under the key clone_mutual, last confirmed 14 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 20:00 | 22,971 | -54 |
| 10 Nov 2026, 12:45 | 23,025 | -76 |
| 9 Nov 2026, 02:47 | 23,101 | -54 |
| 7 Nov 2026, 20:21 | 23,155 | -90 |
| 6 Nov 2026, 15:47 | 23,245 | -55 |
| 5 Nov 2026, 13:51 | 23,300 | +1,166 |
| 4 Nov 2026, 10:39 | 22,134 | -62 |
| 3 Nov 2026, 13:06 | 22,196 | -36 |
| 2 Nov 2026, 14:57 | 22,232 | -6 |
| 1 Nov 2026, 11:59 | 22,238 | -17 |
| 31 Oct 2026, 10:36 | 22,255 | -17 |
| 30 Oct 2026, 12:37 | 22,272 | -19 |
| 29 Oct 2026, 11:11 | 22,291 | -7 |
| 28 Oct 2026, 10:19 | 22,298 | -13 |
| 27 Oct 2026, 12:06 | 22,311 | -12 |
| 26 Oct 2026, 09:57 | 22,323 | -1 |
| 25 Oct 2026, 10:28 | 22,324 | -1 |
| 24 Oct 2026, 12:46 | 22,325 | -22 |
| 23 Oct 2026, 15:58 | 22,347 | -12 |
| 22 Oct 2026, 14:45 | 22,359 | first reading |
411 posts held, back to 6 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 106 pages of Telegram’s post history, 20 posts per page.
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 59 of 94 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 411 (6 August 2026 – 13 November 2026) |
| Views total | 153,223 |
| Reactions total | 78 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 03:03 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.
Lifetime counters from Telegram’s own channel header, read 14 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.
Measured directly from 14 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.
434 reactions across 256 posts, in 13 distinct kinds. The most used accounts for 65.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 284 | 65.4% | |
| 👍 | 59 | 13.6% | |
| 🔥 | 54 | 12.4% | |
| 👀 | 12 | 2.76% | |
| 😁 | 6 | 1.38% | |
| 👏 | 4 | 0.922% | |
| 😈 | 3 | 0.691% | |
| 😱 | 3 | 0.691% | |
| 🤩 | 3 | 0.691% | |
| 🥰 | 3 | 0.691% | |
| 😐 | 1 | 0.23% | |
| 😘 | 1 | 0.23% | |
| 🤓 | 1 | 0.23% |
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 259 of the 411 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 434 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 411 most recent posts we hold, published 6 August 2026 to 13 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.
Telegram’s own ‘edited’ marker: 1 of 94 posts held from the last 30 days (1.06%) 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).
🚨 오픈AI, '챗GPT 월렛' 출시 — AI 에이전트가 직접 결제 오픈AI가 AI 에이전트 'dots'가 사용자 대신 물건을 찾아 결제까지 해주는 챗GPT 월렛을 공개했습니다. 카드 정보는 에이전트에 노출되지 않는다고 합니다. • 아멕스·마스터카드·비자와 공동 구축 • 美 Pro 구독자(18세+)부터 순차 적용 • 결제마다 Face ID 등 생체인증 승인 • 실제 카드번호 대신 결제 토큰 사용 · 카드 혜택 유지 ✍️ 막돈 코멘트 챗봇이 '지갑'을 갖기 시작했습니다. 에이전트 커머스가 본격화되는 신호로 보시면 좋겠습니다. 기사원문
❤1
🚨 美 10월 PPI +0.3%, 예상치 하회 (근원 +0.3% · 전년비 +6.5%) 미국 생산자물가가 전월 대비 +0.3%로, 시장 예상(+0.4%)을 소폭 밑돌았습니다. 전년비는 2022년 11월 이후 최고입니다. • 헤드라인 +0.3%(예상 +0.4%·9월 수정치 +1.4%) • 전년비 +6.5%(예상 +6.6%·전월 +6.3%) • 근원 +0.3%(예상 동일)·전년비 +5.0% • BTC ~$69,900 반등 · 10년물 ~5.12% · 나스닥선물 +0.1% ✍️ 막돈 코멘트 헤드라인은 식었지만, 식료·에너지·유통 제외는 여전히 +0.5%입니다. 12월 인상(발표 전 약 90%)을 뒤집기엔 부족해 보이며, 비트 반등은 숨 고르기로 보시면 좋겠습니다. 기사원문
❤1
[ 젠슨황이 부르는 '나만 바라봐' ] AI의 발전 덕분에 이제 이정도 퀄리티의 영상은 손쉽게 만들 수 있게 됐죠👀👀 이제 엔비디아를 사임하신 젠슨황이긴 한데 이 콘텐츠를 보고 즐기는 사람들이 다 외국사람이라 너무 신기합니다🇰🇷 이 노래의 가사를 이해하니까 영상도 만들었을테고 댓글 보면 한국사람보다 외국인들의 반응이 훨씬 많고 다양함🤡🤡 👉 영상 출처 👈
🚨 [업데이트] 앨리스 황 회사, 밀수 엔비디아 칩 조달 (블룸버그) 젠슨 황 사임 하루 만에, 스캔들 중심 인물의 회사가 금지 칩을 상하이 데이터센터에 들였다는 문서가 공개됐습니다. • 메가스피드 연관 상하이 데이터센터에 설치 • 일부 서버는 싱가포르 엔비디아 공식 파트너 경유 • 로이터 "中 금지칩 기반 프로젝트 $3.2B+" • 美 의회 대중 칩 규제 법안 탄력 (로이터) ✍️ 막돈 코멘트 이제 개인 스캔들이 아니라 수출통제 강화 명분이 됐습니다. 中 AI·칩 관련주 변동성 주의하셔야겠습니다. 기사원문
❤1
🚨 만트라(MANTRA), 업비트·빗썸·코인원 동시 상장폐지 8월 해킹 이후 거래유의 종목이었는데, 소명이 부족하다며 3대 거래소가 오늘 16시 일제히 거래지원 종료를 공지했습니다. • 거래종료 12/14(월) 15:00 · 출금 마감 2027/1/13 • 사유: 8/20 체인 해킹(약 7.2억 MANTRA 무단 이동) 미해소 • 빗썸은 리콜(RECALL)도 함께 종료 • 업비트 MANTRA 4.42원 (-10.2%) ✍️ 막돈 코멘트 보유 중이시면 출금 가능한 해외 거래소·지갑을 미리 확인해 두시는 게 좋겠습니다. 기사원문
🚨 비트코인 $70K 붕괴 — 8월 이후 처음 비트코인이 7만 달러 아래로 밀렸습니다. 하루 새 롱 포지션 청산이 쏟아지고 있다고 합니다. • BTC ~$69.9K (24h -5.1%) · ETH ~$1,984 (-3.3%) • 24시간 청산 $6.8억 · 롱 88% • 현물 ETF 5거래일 순유출 ~$14.4억 • 젠슨 황 사임 · MSCI 스트래티지 퇴출 · 12월 금리인상 우려 ✍️ 막돈 코멘트 오늘 밤 22:30 美 PPI 발표가 다음 방향을 가를 수 있습니다. 다음 지지선 $67~68K 주의해야겠습니다. 기사원문
❤1
6 찍었드아....
👍1
앞자리 6 보는건가... ㄷㄷ
👍1
엔비디아로 50배 먹은 사람 등장
👏1
🚨 오픈AI, 中 AI칩·장비 봉쇄 법안 지지 — 젠슨 황 퇴진 후 규제 탄력 오픈AI가 이번 주 미 의회에 대중국 수출통제 법안 3종 지지 의사를 전달했다고 블룸버그가 보도했습니다. • AI 오버워치법: 대중 칩 수출 기준 18개월+ 동결 • 매치법: 中 반도체 장비 구매 제한 • 칩 보안법: 밀수 방지 장치 의무 • 연말 국방수권법(NDAA) 포함 추진 · 앤트로픽도 지지 ✍️ 막돈 코멘트 규제 반대의 최전선이던 황이 빠지자 빅테크 판도가 수출통제 쪽으로 기울고 있습니다. 트럼프 거부권 여부를 봐야겠습니다. 기사원문
Posted without readable text
❤1
💸엔비디아 관련 카더라.txt 1. 자기가 들은 썰에 의하면, 미국 정치권은 이미 6개월 전에 젠슨황의 중국 스파이 이슈를 알고 있었다. 2. 이걸 미국 민주당 주도로 중간 선거 직후 터뜨린 것이다. 3. 터뜨린 이유는 트럼프와 공화당을 견제하기 위함이다. 1) 트럼프가 AI 정책을 주도하는 것을 견제하고 2) 트럼프와 공화당이 선거 패배 이후 외교, 특히 G2 대중국 외교로 정치 난국을 타개하려고 시도할 것인데, 여기서 트럼프의 핵심 카드가 엔비디아 칩과 젠슨황이다. 4. 처음에 중국 스파이 뉴스만 나왔을때는 젠슨황의 해임 가능성은 높게 보지 않았다. 5. 근데 사내 불륜 뉴스가 나오는 걸 보니 젠슨황은 해임될 거라고 본다. (젠슨황 해임 발표 이전에 촬영된 영상임) 그 이유는 미국 기업들은 규정으로 사내 불륜을 해…
Showing the 12 most recent of 411 posts we hold for @lastmoneyalpha. 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.
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.
Republishes 61 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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.
@lastmoneyalpha named 13 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“Web3 & TCG & AI 막돈방” (@lastmoneyalpha), 22,971 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/lastmoneyalpha.
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.