📕 ZCASH, 5만개 소각 논의 ✅ ZCASH 커뮤니티에서 개발 기금으로 포함된 5만개의 ZCASH 를 소각하기로 투표를 시작했습니다. 이는 기금의 55% 에 해당하며 투표 기한은 30일까지입니다. #ZEC #ZCASH
❤3👏1

Channel
@leedogin2
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
15,336subscribers
+110 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001725574634 |
|---|---|
| Type | Channel |
| Username | @leedogin2 |
| Description | #이도진 메타버스 Official 공지방 공지방 : https://t.me/leedogin2 채팅방 : https://t.me/chat_dogin 유튜브 : https://www.youtube.com/@leedogin DM : @leedogin2022 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/leedogin2 |
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 96% 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 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @airdr0p_lab/212383 Nov 2026, 11:54 UTC | @leedogin2/24716 · this entry3 Nov 2026, 12:08 UTC | 1.00 | 14 minutes |
| @airdr0p_lab/212594 Nov 2026, 13:21 UTC | @leedogin2/24744 · this entry4 Nov 2026, 13:53 UTC | 1.00 | 32 minutes |
| @airdr0p_lab/213409 Nov 2026, 02:59 UTC | @leedogin2/24801 · this entry9 Nov 2026, 03:40 UTC | 1.00 | 41 minutes |
| @cryptocurrencymage/244936 Nov 2026, 13:21 UTC | @leedogin2/24781 · this entry6 Nov 2026, 14:12 UTC | 1.00 | 51 minutes |
| @cryptocurrencymage/245748 Nov 2026, 14:26 UTC | @leedogin2/24795 · this entry8 Nov 2026, 14:32 UTC | 1.00 | 6 minutes |
| @leedogin2/24785 · this entry7 Nov 2026, 13:05 UTC | @cryptocurrencymage/245839 Nov 2026, 02:48 UTC | 1.00 | 38 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @airdr0p_lab | 15 (8/8 hand-verifiable sample passed) | 1.00 | 14 minutes | @airdr0p_lab (12–3) |
| @cryptocurrencymage | 9 (8/8 hand-verifiable sample passed) | 1.00 | 1.8 hours | @cryptocurrencymage (7–2) |
| @waitstudy | 17 (8/8 hand-verifiable sample passed) | 1.00 | 1.6 hours | @waitstudy (14–3) |
| @WeCryptoTogether | 10 (8/8 hand-verifiable sample passed) | 1.00 | 32 minutes | @WeCryptoTogether (9–1) |
| @mujammin123 | 14 (8/8 hand-verifiable sample passed) | 1.00 | 34 minutes | @mujammin123 (11–3) |
| @minchoisfuture | 15 (8/8 hand-verifiable sample passed) | 1.00 | 28 minutes | @minchoisfuture (14–1) |
| @coinboys | 5 (5/5 hand-verifiable sample passed) | 1.00 | 27 minutes | @coinboys (4–1) |
| @jh_6598 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 11 minutes | @jh_6598 (6–1) |
| @cybertruck666 | 11 (8/8 hand-verifiable sample passed) | 1.00 | 15 minutes | @cybertruck666 (9–2) |
| @Honeyofwhitesocks_2 | 13 (8/8 hand-verifiable sample passed) | 1.00 | 4.9 hours | @Honeyofwhitesocks_2 (8–5) |
| @airdrop_kor | 5 (5/5 hand-verifiable sample passed) | 1.00 | 2.6 hours | this entry (3–2) |
| @BChoSN | 6 (6/6 hand-verifiable sample passed) | 1.00 | 32 minutes | @BChoSN (4–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. 15 of the 20 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 228 comparable posts for this entry, running 5 August 2026 to 11 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 keys clone_copy · clone_mutual · clone_source, last confirmed 12 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 |
|---|---|---|
| 11 Nov 2026, 14:09 | 15,336 | -25 |
| 9 Nov 2026, 21:17 | 15,361 | -24 |
| 8 Nov 2026, 10:07 | 15,385 | -8 |
| 7 Nov 2026, 07:47 | 15,393 | -16 |
| 6 Nov 2026, 08:00 | 15,409 | -7 |
| 5 Nov 2026, 09:10 | 15,416 | -8 |
| 4 Nov 2026, 09:01 | 15,424 | -8 |
| 3 Nov 2026, 05:59 | 15,432 | -5 |
| 2 Nov 2026, 08:26 | 15,437 | -4 |
| 1 Nov 2026, 11:37 | 15,441 | -1 |
| 31 Oct 2026, 14:07 | 15,442 | -6 |
| 30 Oct 2026, 16:17 | 15,448 | -10 |
| 29 Oct 2026, 12:49 | 15,458 | -6 |
| 28 Oct 2026, 13:56 | 15,464 | -7 |
| 27 Oct 2026, 14:27 | 15,471 | -9 |
| 26 Oct 2026, 12:16 | 15,480 | -6 |
| 25 Oct 2026, 14:17 | 15,486 | +7 |
| 24 Oct 2026, 17:10 | 15,479 | -5 |
| 23 Oct 2026, 19:29 | 15,484 | -8 |
| 22 Oct 2026, 20:50 | 15,492 | first reading |
626 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 72 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 153 of 173 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 November 2026 |
|---|---|
| Posts held | 626 (5 August 2026 – 12 November 2026) |
| Views total | 130,744 |
| Reactions total | 702 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 06:58 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 12 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 25 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.
5,273 reactions across 571 posts, in 22 distinct kinds. The most used accounts for 41.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,164 | 41.0% | |
| 👍 | 1,156 | 21.9% | |
| 👏 | 957 | 18.1% | |
| 🔥 | 539 | 10.2% | |
| 😱 | 179 | 3.39% | |
| 👎 | 69 | 1.31% | |
| 🖕 | 61 | 1.16% | |
| 😁 | 52 | 0.986% | |
| 🤔 | 15 | 0.284% | |
| 😢 | 13 | 0.247% | |
| 🤯 | 13 | 0.247% | |
| 🤣 | 8 | 0.152% | |
| 🤬 | 8 | 0.152% | |
| 🥰 | 8 | 0.152% | |
| 😭 | 6 | 0.114% | |
| 😨 | 5 | 0.095% | |
| 🙏 | 5 | 0.095% | |
| 🤮 | 5 | 0.095% | |
| 🫡 | 5 | 0.095% | |
| 👌 | 3 | 0.057% | |
| 2 further kinds | 2 | 0.038% |
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 596 of the 626 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 5,500 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 626 most recent posts we hold, published 5 August 2026 to 12 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 626 most recent posts we hold, published 5 August 2026 to 12 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 31 of 173 posts held from the last 30 days (17.9%) 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).
📕 ZCASH, 5만개 소각 논의 ✅ ZCASH 커뮤니티에서 개발 기금으로 포함된 5만개의 ZCASH 를 소각하기로 투표를 시작했습니다. 이는 기금의 55% 에 해당하며 투표 기한은 30일까지입니다. #ZEC #ZCASH
❤3👏1
Legion에서 콘텐츠 및 그로스 총괄 채용 중 이라고 합니다 https://x.com/legiondotcc/status/2120556864811213271
❤2
오늘 본 가장 골때리는 글 * 세무사 시험에서 역대 수석이 80점 남짓인데 갑자기 99.9점이 나와서 AI 안경 사용 걸리게 됨. 불법을 저지르려고 해도 멍청하면 답이 없다
❤1
승리자는 역시 본처인건가
❤6
남자는 세가지만 조심하면 된다고 했거늘... 술,여자, 도박 젠슨 황 두 번째 불륜설 터짐
👏3
MSCI, Strategy(MSTR) 지수 편출 공식 발표 오늘 11월 12일 오전 7시 이후 발표된 결과에서 MSTR의 MSCI 지수 편출이 확정 #스트레티지
❤2😱2
ㅁㅊ
❤4👏2
지금 보니까 여기 지갑에 1BTC 있는데 제일 먼저 찾고 싶네요
❤2🔥1
쌀먹. 찍먹 꾹꾹 챙겨보기 라이브 페이지 좀 특이하긴 한데 리워디에서 '해킹 이벤트'를 진행한다고 합니다. BTC, ETH 보관된 챌린지 지갑 복구 구문을 단계적으로 공개하는 방식으로 12개 복구 구문을 완성하면 되는 이벤트. * 상품 : 1BTC or 1ETH - 각 지갑에는 1비트, 또는 1 이더가 있음 - 12개 단어 먼저 완성해 자금 옮기면 완료 - 11/11 21:00 - 11/25 20:59 KST - 3일마다 한 단어씩 시드 구문 공개 예정 - 유튜브 라이브에서 공개되고, 12개 모두 공개되면 자금 이동 * 유튜브 라이브에서 순차적으로 공개되는 문구 확인 * 공개 단서 바탕으로 단어 추론해서 12개로 구성된 복구 구문 완성 * 방송 시작 후 3일 간격으로 복구구문 일부 단어 순차 공개 * 3일차(1차 힌트), 6일차(2차…
❤1👏1
오..??? Jumper 드디어 나오나보네요 계속 미루는거보다 슉슉 빠르게 TGE하는게 훨씬 낫긴한듯. TGE 시점이 다가오는거 같아서 Jumper 지표 대강보니까 꾸준히 일정 볼륨은 유지되는듯. 대부분 볼륨이 Bridge에서 나오고 (한달에 약 665M) 덱스는 180m , 퍼프는 80m정도 수준.. 전체 브릿지 어그리게이터 놓고보면 요정도 느낌 1등 Lifi (모회사) 2등 0x 3등 소켓 4등 점퍼 레기온 세일/에드가 어떻게 나올진 모르겠지만 일단 들어가셨던 분들 다 건승기원
❤6🔥1
자발적 퇴사해도 월 100만원 받는 퇴직급여 제도 검토 출처 - 기존 : 원칙적 비자발적 퇴사자에게 지급 - 변경점 : 자발적 퇴사 청년까지 확대 고려(35세 미만)
❤2👏1
쌀먹 노려볼 수 있는 콘텐츠 챌린지 : Alphio 얼마 전 우리 채널에서도 이벤트를 진행했던 에이전트 트레이딩 플랫폼 Alphio 에서 트레이딩 콘텐츠 챌린지를 진행합니다. - 기간 : 11/10 - 11/29 23:59 KST - 보상 : 1등 $200, 2~20등 각 $10 - 에이전트 트레이딩 활용 소감 X 게시글 작성 - 매매 화면 스크린샷 + @AlphioAI 태그 ✔참여 방법 가이드 - 팔로우 l 디스코드 입장 l Alphio 사용해보기 - Agents 탭의 Meme Agent·Perps Agent 활용 - X 글 작성 후 Discord 의 Sharing 탭에 X에 포스팅한 링크 입력 - 네이버폼 제출
❤1
Showing the 12 most recent of 626 posts we hold for @leedogin2. 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.
@leedogin2 edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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 110 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 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.
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.
@leedogin2 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.
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.
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.
This channel appears in 21 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“이도진 메타버스 공지사항 🦅” (@leedogin2), 15,336 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/leedogin2.
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.