Been too long and too much drama, but here's a really good summary that I feel compelled to share: https://twitter.com/mrjasonchoi/status/1592502785873825794

Channel
ChainLeaks
@chainleaks
On this record: Topic · Growth · Engagement · Posts · Cite this entry
782subscribers
-16 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001143399619 |
|---|---|
| Type | Channel |
| Username | @chainleaks |
| Created | Between 1 April 2016 and 30 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/chainleaks |
Topic
Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 13:19 | 782 | -3 |
| 28 Sept 2026, 00:37 | 785 | -6 |
| 12 Sept 2026, 00:21 | 791 | -2 |
| 3 Sept 2026, 20:55 | 793 | -2 |
| 20 Aug 2026, 06:23 | 795 | -1 |
| 13 Aug 2026, 17:38 | 796 | -2 |
| 6 Aug 2026, 18:01 | 798 | no change |
| 6 Aug 2026, 17:50 | 798 | first reading |
Engagement
20 posts held, back to 20 May 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 15 November 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
Merry Christmas!
What a chart. Not going to give him undue attention, but P**n is at it again.
https://twitter.com/CryptoConjurer/status/1467246945790054406
Getting blamed because Z2O mooned and it's our fault that the data discouraged others. If you want to ape, ape. Our analysis shows it's not safe. Don't blame others for your own actions. Many scams do well, many others rug. Better rr out there.
In case some people say it's a presale, whatever. Even if it was a "presale", those tokens should be vested, similar to pOhm. Right now they're essentially floating tokens. Staked doesn't matter, they can be unstaked at anytime to be dumped.
Arbitrum soft scam Z2O (OHM Fork). Creator "contributes" 84.5K MIM (premine essentially) to get 84.5K Z2O. Sends it to a bunch of random wallets, some to sell and some to stake. Fair launch. Here're the addresses: Z2O Balances: 1. address: 0x131b4e746ca5a5a8be68d2bb5f5a8533a4dd99c1 | token balance: 0.097745165 2. address: 0x40c938444c725ea6eb6992ca71f94b6945b43335 | token balance: 2270.873153525 3. address: 0x2bdc4e…
Scams happen everyday, even when you don't hear about it. https://medium.com/@danielvidaldev/crypto-megalomaniac-76ad30889bbd
DeFiance is one of the best strategic VCs ever. https://twitter.com/cryptospider1/status/1419808458908438530
Vinny reached out personally - The issue was never with pooling in the first place and that was clearly stated in the document shared as well. The issue was around pooling to non-approved participants. Hope this clarifies the issue for anyone who’s unhappy with the situation and thinks we’re taking sides (lol what side really). Again, if you’re in the original affected pools we hope your funds are safe. Vinny has c…
Posting that without context but as a follow up to the whole DHC <> Moonwhale <> CRT fiasco. Make of it what you will.
Some pools are more equal than others.
Showing the 12 most recent of 20 posts we hold for @chainleaks. 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.
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“ChainLeaks” (@chainleaks), 782 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/chainleaks.
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.