Channel
@techleaks24
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
578subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002148202135 |
|---|---|
| Type | Channel |
| Username | @techleaks24 |
| Description | 如果中本聪这么做了，必然有他的道理。 |
| Created | Between 1 May 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/techleaks24 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 03:21 | 578 | no change |
| 7 Aug 2026, 13:33 | 578 | first reading |
19 posts held, back to 27 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 1 pageof 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 19 (27 July 2026 – 7 August 2026) |
| Views total | 3,806 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 03:21 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 8 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.
我尽量做到最大程度的客观和基于事实。我从来没认为中本聪是中国人，或者来自亚洲。但中国在比特币早期发展阶段扮演了关键角色，而这一点经常被 Palantir-Epstein 控制的西方叙事制造者刻意淡化和一笔带过。这是没人能够否认的事实。 在比特币存在的最初十年里，大部分算力都来自中国。 我也知道一个事实：DERO 的技术是比特币的直接演进。中本聪之所以把它命名为 DERO，是因为它是英文单词 REDO（从头重做、重新构建某件事）的字母重排。 无论是谁创造了比特币——第一个数字现金系统——并分析了比特币存在的所有弱点，然后创造了 DERO，使这些经过多年暴露出来的弱点在 DERO 中一个都不存在。 如果 DERO 是在亚洲开发的，那么这就证明中本聪也来自世界这一地区。这也解释了为什么如今西方的开发者圈子里没有人真正理解或欣赏 DERO 的技术。他们的技术认知落后于打造 DERO 的那群人整整十年。就像 2009 年时，他们落后于中本…
请在其他华人社群分享这个消息。我发现这里有一些华人读者。CoinEx 试图窃取中国用户的 Dero。
赶紧把你的 Dero 从 CoinEx 提出来，别白送给 CEX。Dero 是中本聪对比特币的终极重构。那是 Dero 在 WAIC 的标志。
How I'm walking after buying some Redo under 10¢
Bottomline: Captain spent the premine's 2M coins in the previous bull, and then minted another 2M to get a refund because of course this is the magnum opus of crypto and he deserves a stake in his magnum opus, especially since it's not just his magnum opus but for the entire privacy space because nothing else comes close to it in terms of tech. I accept it, I approve of it (better this than having to email VCs for f…
I know what Captain did based on incentives, timing of events and everything that unfolded afterwards. And I'm ok with it. Captain didn't ask for VC funding so I guess he decided to fund his operations this way, it makes sense. That's incentive. Then I know there is a transaction where an account that never received any money appears as spender, and after that spends millions of coins. Unless a transaction was pruned…
Top g, I'm not suing anyone, so I don't have to compare ciphertexts myself to mathematically prove anything because I'm not going to court. I'm a free man, and I respond like a capitalist in a free world, I decide accordingly based on what I think is the right thing to do. Example: you got the spouse acting weird that is served with divorce papers and shouts "YuO caN'T proVe it!!". When she/he goes with her phone in…
Oh, and you don't have to take my word for it, in case my Coinkite point seems debatable because how would I know since I'm not a dev, Gregory Maxwell himself explained this in a Reddit thread about Coldcard. Now question, has anyone of the integrity guys inspected the precompiled binaries in circulation when the exploit transaction happened in late 2022, or are they relying on the open source code only? Nobody has …
Around 600 BTC stolen from Coinkite, because of a bug in the randomness generator. Interestingly, the discovery of this bug was delayed because people read the open source viewable code like sheep without ever checking the binaries and inspecting the binaries would have made it much easier to detect the bug. In the open source code it was more tricky because the buggy part looked plausible at first glance, in the pre…
Thank you for the reply, Ahmed. I am not mixing anything, you're the one mixing up a historical artefact with cryptographic proof. Did the transaction pass verification with the network of precompiled, non reproducible nodes in late 2022? Yes it did. Does that mean it passed verification with the open source proofs? No it does not, because precompiled binaries were not reproducible at the time so we have no guarantee…
Can someone from China or North Korea reading my blog push around the Redo inflation bug story? Hopefully some OG there can reach the low level shills through the appropriate backchannels to redpill them that the bug is real and done by Captain to mint 2M coins to refund himself the premine. Shills are trying to act sophisticated by implying that if you can't find a bug in the code, then supply is auditable because …
To all those devs saying I've gone delulu, Dero is not Satoshi's Redo, it does not eliminate all the attack vectors, I'm just an AI educated shill, dero is just an inflation scam etc. Ok. Let's assume for a moment you're right. Then what was Dero's logo doing at the WAIC? You know Xi Jinping opened the WAIC, right? You know AI is part of China's strategy to win approval for the One China policy, right? You know the …
Showing the 12 most recent of 19 posts we hold for @techleaks24. 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 — 75,524 of 1,160,990entries 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Techleaks24🇵🇸🇹🇼” (@techleaks24), 578 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/techleaks24.
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.