Variational 예정대로 TGE 준비중 앞서 토큰노믹스 업데이트에서 예고했던 주요 파트너십 발표도 예정대로 준비 중이며, 이번달 중 추가 소식을 공개할 예정
👍1

Channel
@jammin0720
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
5,703subscribers
+2,195 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002179206614 |
|---|---|
| Type | Channel |
| Username | @jammin0720 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/jammin0720 |
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 14 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 23:37 | 5,703 | -26 |
| 5 Nov 2026, 15:57 | 5,729 | -11 |
| 2 Nov 2026, 15:47 | 5,740 | -29 |
| 30 Oct 2026, 14:15 | 5,769 | -130 |
| 27 Oct 2026, 10:06 | 5,899 | -9 |
| 24 Oct 2026, 18:57 | 5,908 | -7 |
| 21 Oct 2026, 22:28 | 5,915 | -28 |
| 18 Oct 2026, 22:54 | 5,943 | -17 |
| 16 Oct 2026, 03:57 | 5,960 | -36 |
| 13 Oct 2026, 00:27 | 5,996 | -204 |
| 6 Oct 2026, 13:37 | 6,200 | +648 |
| 29 Sept 2026, 09:02 | 5,552 | +1,972 |
| 19 Sept 2026, 00:57 | 3,580 | -3 |
| 15 Sept 2026, 01:21 | 3,583 | +1 |
| 11 Sept 2026, 14:20 | 3,582 | +8 |
| 6 Sept 2026, 15:41 | 3,574 | +18 |
| 2 Sept 2026, 02:34 | 3,556 | +4 |
| 30 Aug 2026, 04:56 | 3,552 | +5 |
| 26 Aug 2026, 19:43 | 3,547 | -8 |
| 23 Aug 2026, 09:37 | 3,555 | first reading |
46 posts held, back to 2 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 4 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 5 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 46 (2 August 2026 – 4 November 2026) |
| Views total | 8,385 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 19:17 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.
Measured directly from 1 video 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.
32 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 65.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 21 | 65.6% | |
| 😱 | 4 | 12.5% | |
| 👍 | 2 | 6.25% | |
| 😭 | 2 | 6.25% | |
| 🤔 | 2 | 6.25% | |
| 🔥 | 1 | 3.13% |
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 16 of the 46 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 46 most recent posts we hold, published 2 August 2026 to 4 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: 4 of 19 posts held from the last 30 days (21.1%) 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).
Variational 예정대로 TGE 준비중 앞서 토큰노믹스 업데이트에서 예고했던 주요 파트너십 발표도 예정대로 준비 중이며, 이번달 중 추가 소식을 공개할 예정
👍1
QFEX는 지표만 봤을때 계속 우상향중 거래량의 70프로 이상이 주식이라 주말에 거래량이 떨어지는건 어쩔수 없는듯 대신 OI자체는 줄어들진않고 오히려 상승하는 추세 저도 QFEX를 하고 있지만 이런 계단식 성장은 보기 좋은듯
이번 바이낸스 해킹사고 글은 정리하는 와중에 뭐가 많이나와서 시간이 꽤 오래걸렸네요. 요즘은 일회성 소비보다는 두고두고 읽을 수 있는 글을 쓰기위해 고민하고 있는데 그렇다보니 쓰는데 시간이 좀 걸리는 것 같습니다. 이번 글은 사고에 대한 정리보다도 특히 세계 최강 해커들이 달아준 코멘터리의 내용이 좋아서 함께 읽어보시면 좋을 것 같습니다. https://research.4pillars.io/ko/research/reflections-on-the-binance-exploit
❤1
https://hachiware-tone.vercel.app/ ㅋㅋㅋㅋㅋ하치와레 화법으로 바꿔준다네용 출처
SlopCash Auction Early Bid 참여 조건은 한국시간으로 11월 6일 새벽 2시에 당일 공개 참여 자격 인증에는 Umia 확장 프로그램으로 생성한 증명이 필요하다고 하니 미리 설치해두시면 좋겠습니다
Variational의 거래량은 점점 하락세를 보여주고 있네요 > 10월 1일 - 10월 8일: 약 $20.8B > 10월 8일 - 10월 15일: 약 $18.6B > 10월 15일 - 10월 22일: 약 $18B > 10월 22일 - 10월 29일: 약 $14.5B 점점 거래량이 하락세를 보여주고 있는데 하락세를 보여주는 이유는 Q3에 에어드롭이 예정이였는데 파트너쉽 계획이 바뀌면서 Q4로 밀린 경향이 있지 않나 싶네요 어느분들은 지금이 포인트 파밍하기 제일 좋은 시즌이라 말씀도 하시니 한번쯤 파밍해보시는것도?
VC별로 투자한 토큰이 업비트·빗썸·바이낸스·코인베이스에 얼마나 상장돼 있는지 비교해볼 수 있는 대시보드를 만들어봤습니다 업비트 상장 비율 (포트폴리오 20개 이상) 1. Lightspeed Faction 64% (18/28) 2. Standard Crypto 57% (13/23) 3. Variant 57% (13/23) 4. Paradigm 53% (20/38) 아직 업비트에 $ZEC $HYPE $BNB가 없는 게 신기하네요 👻 KDP 사이트
아서헤이즈가 이끄는 FLOP 과연 노드 메타가 올지???? 테스트넷은 11월 초에 시작하고 90일 정도 운영 예정이니 대략 2월초~3월쯤에 런칭을 하는거 같아요
FLOP devnet 오픈을 했는데 보상은 안준다고 확실하게 표기는 해놨지만 요즘 AI 잘되어있으니 서버 빌려서 한번쯤은 뚝쓰딱스 해보는거 나쁘진 않은듯 X원문
익스텐디드는 마지막으로 포인트 뿌렸네요 진짜 곧곧 나오는거 같은데 시장이 안좋아서 성과가 좋을진...잘되길바랍니다
가만 생각해보면 요즘 크립토 시장 분위기가 영 좋지 않은듯 하이퍼리퀴드 미국 시장 진출 소식에 분위기 좀 살아나나 싶었는데 바이낸스 해킹 터지면서 다시 안 좋아진 느낌 개인적으로도 슬럼프가 온 건지 성적이 영 좋지 않음 1%~2% 먹으려다가 5% 뱉는 경우도 허다해서 당분간 사이즈 최대한 줄일 생각 일단 욕심 내려놓고 멘탈 회복하면서 천천히 감부터 되찾아보고 있음 다들 화이팅하시죠
🔥1
Shaw는 결국 펌프펀 리버스 엔지니어링을 성공했군요. 아예 바이트 숫자까지 같은 완전히 똑같은 코드로 구현했다는듯. 이걸 재미로만 하는게 아니라, Shaw는 프로젝트를 오픈코드화 한다음 AI에이전트들에게 수없이 스트레스 테스트를 시키는 것이 최고의 해킹방지 방법이라고 생각하는듯. (자기가 할 수 있으면, 북한도 당연히 가능하다는 논리) 다음 리버스 엔지니어링 도전은 '하이퍼리퀴드'라고 합니다. https://x.com/shawmakesmagic/status/2116914208541696119
Showing the 12 most recent of 46 posts we hold for @jammin0720. 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.
Republished by 55 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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.
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.
@jammin0720 named 1 handle 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.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Zi존파워잼민” (@jammin0720), 5,703 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/jammin0720.
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.