이런상황이 진짜 일어나는구나
❤1
Signed 팡팡 Pang.xx

Channel
@cryptopangpang
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
11,524subscribers
-102 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001851134675 |
|---|---|
| Type | Channel |
| Username | @cryptopangpang |
| Description | 돈 벌줄 모라오 돈되는거 할줄 몰라요 Ann : https://t.me/cryptopangpang Chat : https://t.me/pangpangchat 문의 : @Pangpangcrypto |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/cryptopangpang |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 14:33 | 11,524 | -4 |
| 1 Sept 2026, 15:34 | 11,528 | -5 |
| 31 Aug 2026, 17:17 | 11,533 | -5 |
| 30 Aug 2026, 14:47 | 11,538 | -7 |
| 29 Aug 2026, 14:26 | 11,545 | -2 |
| 28 Aug 2026, 13:03 | 11,547 | -1 |
| 27 Aug 2026, 12:03 | 11,548 | +1 |
| 26 Aug 2026, 12:04 | 11,547 | -2 |
| 25 Aug 2026, 08:46 | 11,549 | -6 |
| 24 Aug 2026, 05:57 | 11,555 | -7 |
| 22 Aug 2026, 15:58 | 11,562 | -8 |
| 21 Aug 2026, 08:18 | 11,570 | -2 |
| 20 Aug 2026, 09:48 | 11,572 | -5 |
| 19 Aug 2026, 10:24 | 11,577 | -3 |
| 18 Aug 2026, 12:43 | 11,580 | -7 |
| 17 Aug 2026, 12:26 | 11,587 | -11 |
| 16 Aug 2026, 03:47 | 11,598 | -3 |
| 14 Aug 2026, 17:06 | 11,601 | +8 |
| 13 Aug 2026, 09:04 | 11,593 | -1 |
| 12 Aug 2026, 09:16 | 11,594 | first reading |
46 posts held, back to 28 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 44 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 29 of 33 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 46 (28 July 2026 – 2 September 2026) |
| Views total | 49,989 |
| Reactions total | 65 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 23:51 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 2 September 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.
107 reactions across 38 posts, in 8 distinct kinds. The most used accounts for 72.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 77 | 72.0% | |
| 👍 | 13 | 12.1% | |
| 👀 | 9 | 8.41% | |
| 👻 | 2 | 1.87% | |
| 🔥 | 2 | 1.87% | |
| 😭 | 2 | 1.87% | |
| ❤🔥 | 1 | 0.935% | |
| 🥰 | 1 | 0.935% |
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 40 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 107 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 28 July 2026 to 2 September 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.
이런상황이 진짜 일어나는구나
❤1
Signed 팡팡 Pang.xx
cro측에서 tectonic exploit 이전으로 블록을 롤백하면서 해킹 시간 동안 타체인 → cro로 cctp 통해서 브릿징한 모든 트잭이 롤백 해당 트잭들이 source chain에서 burn 된상태로 processing 트잭으로 남아있었는데, 현재 체인 복구되면서 cctp측에서 해당 트잭들 모두 재민팅 가능하도록 해줌 당시 해커가 해킹자금을 relay로 무작정 빼면서 usdc → usdt 아비트라지가 가능했는데, 돌린 바퀴수만큼 돈복사 https://debank.com/profile/0x598b625542604fcc925997402694aa4ffdda6250/history 해당 지갑은 당시 10~30% usdt 아비트라지 수익 + 돌린 횟수만큼 돈복사 60만불 돈복사...
❤2
Signed 팡팡 Pang.xx
☑️ 내일부터 Linera / Ethos 세일시작. 각종 분석 모아보기 - Ethos 총 공급량의 20% 판매 경매 방식 시작 FDV $1M 최대 FDV $99M -15% 까지 하방보장(85% Price Guarantee) 개인적인 적정 세일가격 40M 🚀 관련포스팅 - Linera FDV: $160M 가격: $0.16 총 공급량: 10억 LNRA 목표 판매: 2% = 약 $3.2M 최대 판매: 5% = 약 $8M Badge Guaranteed Allocation 먼저 배정하고 이후 남은 물량을 Open Pool에 Pro-rata 배정 (생태계 참여하면서 뱃지모은사람들 먼저 얼로케이선 나눠주고 남은 물량세일) 🚀 관련포스팅
❤1
Signed 팡팡 Pang.xx
TectonicFi 대규모 익스플로잇/해킹이 발생 사건 핵심 요약 공격 방식: TONIC(거버넌스 토큰) 유동성이 매우 얇고 collateral factor가 있는 점을 이용 공격자가 TONIC 가격을 단시간에 크게 펌핑(약 100배 수준) → 부풀려진 가격으로 담보 맡김 → 다른 자산 대출을 싹 빼가는 price manipulation / thin-liquidity + weak-oracle 공격 피해 규모: 온체인 추정 약 $66M~$75M 체인 전체 중단(halt) 전 공격자가 Ethereum으로 약 $6M만 브릿지 나머지 상당액은 Cronos에 남아 있음 현재:Cronos 네트워크 일시 중단 익스플로잇 크로노스 지갑 크로노스 지갑2 브릿지 한 이더 지갑
❤1
Signed 팡팡 Pang.xx
해당될 수 있는 카드 (Rain 인프라를 사용하는 곳) Etherfi, KAST, Plasma One, Tria, XPlace, Jupiter, Avalanche Card, Oobit, Avici, Hyperbeat, Lava, Peanut, Kolo 예전에 한번 쭉 조사할 때 이더파이는 아니라고 찾아봤던거같은데 고객사 명단 체크해보니 Rain 사용하고 있군요. (*결제 레일만 쓴다고 알고 있긴 합니다) Tria 외에는 아직 드레인 소식이 없지만 일단 카스트 등등도 전부 퇴각해두시는걸 추천합니다.
❤1
Signed 팡팡 Pang.xx
RAIN측 공지 - "솔라나 컨트렉트 구버전의 취약점 문제" 레인측 문제가 맞았네요 오마갓.. 쿨리파 문제 생길 때 레인부터 걱정됐던게 기우가 아니었구나 🥵 https://x.com/raincards/status/2093435073081053518
Signed 팡팡 Pang.xx
☑️ 오늘부터 1주일간 누구나 가차 참전(링크) 크림(KREAM)에서 TCG 가챠 뽑기가 오픈되었습니다. 누구나 매일 1회 참여 가능하므로 참여해보세요 - 일정 : 8/28 11:00 - 9/4 10:59 - 매일 오전 11시 1회 응모가능 - 매일 변경되는 가차 라인업(매일 3명) 1분 투자지만 아이디 있는 분들은 매일매일 참여해보세요
❤2
Signed 팡팡 Pang.xx
UMIA 어디서 1M 지갑 와서 박혀버렸는데 100불 먼저 보내는 조심성 머지, 돌다리도 두들겨보는거봐라...
❤1
Signed 팡팡 Pang.xx
곧 시작되는 umia 세일은 페이지 접속하시면 화리 물량을 확인할 수 있어요. 에코 , 메타다오 등등을 쓰신분들이라면 얼리버드에 최대 5k 까지 밀어 넣을수 있습니다. 들어가기 앞서서 한가지 설명드리면 이게 CCA 방식이고 인당 5k 로 FDV 대비해서 캡이 굉장히 후한편이라.. 실제로 5k 예치해도 얼리버드 기간동안 체결되는건 500불 이하일거라고 생각하면 될거 같습니다. 대강 2밀 모금 목표인데, 인당 5천불이면 400명만 커밋해도 끝이라 그 이후부턴 비례배분 될텐데 실제 커밋은 500달러 이하로 예상되어요 당연하게 6밀 벨류에 5k 다 커밋시켜주면 인당 토큰의 0.08% 수준을 다 주는거라.. 말이안되고, 그냥 얼리버드도 비들패드세일 생각하시면 될거 같습니다 진짜 물량을 확보하고 싶다면, 얼리버드 보단 아마 퍼블릭에 크게 …
❤2
Signed 팡팡 Pang.xx
🟢 Umia, $UMIA 토큰 세일페이지 오픈 ✅ $UMIA 세일 정보 -네트워크 및 참여 자산: Base USDC -총공급량: 50M UMIA (세일 물량 34.6% 17.3M UMIA) -가격: $0.12 (FDV $6M) ~ $0.36 (FDV $18M) -최소 모집액: $2M -최대 모집 가능액: 약 $6.2M -베스팅: TGE 100% ✅ 일정 -Early Bid: 8월 27일 오전 1시(KST) -Public Round: 8월 29일 오후 9시(KST) -경매 종료 및 거래 시작: 9월 2일 오후 9시(KST) -Early Bid는 zkTLS를 통해 자격을 인증한 지갑만 참여 가능 ✅ 경매 방식 -Uniswap의 CCA(Continuous Clearing Auction) 방식 진행 -참여자는 사용할 USD…
Signed 팡팡 Pang.xx
네린이 reUSD 청산으로 레전드 수익 고백해서 봄 대량 청산 원인 원래 PT-reUSD 가격은 PT/USDC= PT/reUSD x reUSD/USD x USD/USDC 이어야 하는데 지금 사실상 PT/reUSD 가격만 반영하고 $1.095/reUSD leg가 계산에서 빠짐. PT fixed yield 10.5%라 만기 할인율 반영하면 0.97이니 그냥 그 가격만 그대로 반영된 값인가봄? 청산 보너스도 2.6%인데 오라클 자체가 PT를 지금 8.7%정도 싸게 계산하고 있어서 합하면 사실상 보너스 12% 짜리로 오늘도 윈뮤 회식날일듯 == 근데 0x854e3f3b521dbae34cb111ebef0dce41d8b5690d 얘가 그냥 YT매수로 PT덤핑하면서 디페깅 트리거하고 LLTV max 루핑한 애들 청산 트리거하고 가져간듯? 오라클…
❤1
Signed 팡팡 Pang.xx
🚨빗썸거래소에서 코인 출금으로 인해 서비스 이용제한(영구정지) 통보를 받았습니다. ✍️한 줄 요약 반복적인 코인 출금으로 고객확인 요청 및 출금정지 조치를 받은 후 요청받은 모든 서류(54건)를 제출했지만, 추가 소명 기회 없이 '자금출처 확인 불충분'을 이유로 1개월 후 빗썸 서비스 이용제한(영구정지) 예정 통보를 받았습니다. 정당한 수수료 및 높은 출금 수수료(1%)를 내면서 정상 출금을 하였는데 정지가 되었습니다. 정지 후에는 가상자산 매도 및 원화 출금만 가능하여서 보유하던 가상자산을 빗썸에서 다른 거래소보다 싼 가격에 매도하면서 700만원 상당의 손해를 입었습니다. 오렌지 등급(1달 거래 100억이상)조차 의미가 없었고, 8.28일 이후로는 로그인도 제한된다고 합니다. 📅진행 경과 7월 1일: 반복적인 코인 출금 관련 1차 주의 …
❤6
Signed 팡팡 Pang.xx
Showing the 12 most recent of 46 posts we hold for @cryptopangpang. 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.
Citation-graph rank — 289,629 of 1,629,808 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 3 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.
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 5 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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“돈버는 작당모의” (@cryptopangpang), 11,524 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/cryptopangpang.
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.