4 measurements spanning 3 days. 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 6,767–6,769 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 01:51
6,767
-2
7 Aug 2026, 23:47
6,769
+2
7 Aug 2026, 15:16
6,767
no change
7 Aug 2026, 15:07
6,767
first reading
Engagement
18 posts held, back to 5 June 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 9 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
1.42%
avg views ÷ 6,767 subscribers
Avg views / post
96.2
6 posts measured
Reaction rate
1.05%
reactions ÷ views · ER floor
Posts in window
6
of 18 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 3 of 6 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 30 July 2026
Posts held
18 (5 June 2026 – 30 July 2026)
Views total
577
Reactions total
4
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 02:49 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
146
Videos
5
Links
112
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
3
75.0%
👍
1
25.0%
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 3 of the 18 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 5 June 2026 to 30 July 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.
pcaversaccio가 이더리움 재단의 새 보드진 멤버로 조인했습니다.
pcaversaccio는 SEAL 911의 코파운더로 유명한 보안 엔지니어입니다. SEAL 911은 가상자산 프로젝트가 해킹, 키 탈취, 피싱, 스마트컨트랙트 취약점 등 긴급 보안사고를 당했을 때 검증된 보안 전문가들과 연결해 주는 무료 24시간 긴급대응 조직으로, 이제껏 굵직한 해킹에서 큰 역할을 해온 곳입니다. 이외에도 그는 Vyper나 CREATEX 등 오픈소스 등에서 큰 기여를 해오며, 꽤 오랜 기간 이더리움에 발자취를 남겨 왔습니다.
pcaversaccio는 이전부터 트위터에 매우 강경한 어투로 사이퍼펑크적 스탠스를 내비쳐온 바 있습니다. 에릭 휴즈의 사이퍼펑크 매니페스토를 재해석한 'The Ethereum Cypherpunk Manifesto'를 발표하기도…
Robinhood - CashCat 온체인 분석 시리즈 목차
1. Cashcat은 어떻게 200M을 갔나?
- 자금 유입 phase 1, 2
- 세력의 존재 근거들. 재단 or 자금세탁?
2. Dev cluster 분석
- 총 얼마 벌었나?
- 보유량/매매 패턴
3. 천상계 플레이 다시보기
- 빛
- 패턴분석
4. 블록타임/시기별 유입과 수익률 분석
- private 런칭시기 / Noxa,CC배포 전후 / public 후
5. 밈코에 대한 접근
- 반면교사
6. KOL 클러스터 조사
7. 마무리
- 툴 링크
- why?
If you're worried that AI will replace you, read this post - especially if you work a 9-to-5 job.
A roadmap to make sure you never run out of money.
Based on my friend's experience, it took him only 3 months to learn AI, and he made the full transition to freelancing.
https://x.com/AlexFinn/status/2079377591522463813?s=20
Base가 지난주 발생했던 2번의 메인넷 중단 사고Postmortem을 공개했습니다.
결론부터 말하면 해킹도 아니고 합의(Consensus)가 깨진 것도 아니었습니다. 문제는 시퀀서(Sequencer)의 버그였습니다. 하나의 잘못된 트랜잭션이 실패 처리되는 과정에서 내부 메모리(journal state)가 제대로 초기화되지 않았고, 그 다음 정상 트랜잭션이 오염된 상태에서 실행되면서 잘못된 블록이 생성됐습니다. 다른 노드들은 당연히 이 블록을 거부했고, 결국 체인이 멈췄습니다.
흥미로운 점은 이 버그가 단순히 "트랜잭션 하나가 실패했다"가 아니라, 실패 이후의 상태를 얼마나 깔끔하게 복구하느냐에서 발생했다는 것입니다. EVM은 트랜잭션이 실패하면 이전 상태로 완전히 롤백되어야 하는데, 내부적으로 접근했던 계정과 스토리지 정보가 일부 남아 …
Three hours ago 10.6K ETH ($18.5M) moved from an address linked to the $575M Hashflare investment fraud after sitting dormant onchain for 3.5 yrs.
In 2025 both co-founders Sergei Potapenko and Ivan Turogin plead guilty and forfeited $450M of assets to the US government.
The entity began laundering funds via HiFiSwap and Near Intents from Ethereum to Bitcoin and began using two instant exchanges.
H/t to Cyvers for …
Showing the 12 most recent of 18 posts we hold for @web3_laborer. 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.
Forward network
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.
Mentions
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.
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 11 August 2026 — this
entry's latest reading, not the date you are reading this.
“이것저것 다하는 방” (@web3_laborer), 6,767 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/web3_laborer.
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.
