Channel
@Mr_H_calls
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
200subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001927282636 |
|---|---|
| Type | Channel |
| Username | @Mr_H_calls |
| Description | New channel for hitman calls. Only the real ones. Twitter: https://twitter.com/HitmanNoLimit |
| Created | Between 1 April 2023 and 31 October 2023— 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/Mr_H_calls |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:31 | 200 | no change |
| 7 Aug 2026, 09:37 | 200 | first reading |
20 posts held, back to 6 May 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.
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 1 July 2026. An engagement rate over an empty window would be a number about nothing.
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. 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.
Measured directly from 2 videos 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.
13 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 46.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 46.2% | |
| 🔥 | 4 | 30.8% | |
| 👍 | 2 | 15.4% | |
| 👏 | 1 | 7.69% |
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 11 of the 20 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 13reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 6 May 2026 to 1 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.
If you think ansem is going to bring memecoins back, you're sadly mistaken. You're falling for a well executed psyop by the pf team to drive people back to Pump. Just another slop narrative.
❤1
Dev update Big progress on the $DarkDrop app. The thing I was wrestling with, making a private send feel like a normal one, is working end to end on devnet now 🔥 Open the app, paste a wallet, hit send. On the other side, funds just show up. No claim codes, no copy-paste, nothing extra for whoever's receiving. The whole flow. send → it arrives → it lands in their wallet, privately, recipient unlinkable on-chain . Und…
🔥2❤1
This is the strongest fix of the day. Ran 8 adversarial cases against the relayer after the hardening pass, all 8 now fail exactly where they should. Replay attempts rejected. Wrong / missing memo rejected. Over-transfer rejected. Decoy instructions rejected. Destination validation enforced. Exact instruction count enforced. The important part isn’t just that the happy path works. It’s that the abuse paths don’t.…
I'm opening a permissionless trusted-setup ceremony for DarkDrop, and we need contributors. Here's what that means and why it matters. DarkDrop uses Groth16 zk-SNARKs to make transfers private on Solana. But every Groth16 system has a catch: the proving keys can only be generated alongside a piece of secret randomness, "toxic waste." Anyone who keeps that secret can forge proofs and mint value out of thin air, sile…
$Darkdrop
❤1
On-chain transparency is a feature for verifiability. For payroll, OTC, and most things people actually move money for, it's a glass piggy bank. $DarkDrop in two minutes. SOL hidden via direct lamport ops. USDC just landed. darkdrop.app 6wKRRP1c2gkWESch723bmgCWiBYiYvn4krspZXdApump
$DarkDrop now supports $USDC Private USDC transfers on Solana. ZK proofs. Trustless. Recipient never signs, never pays gas. Credit note architecture. Same primitive that ships SOL, now extended to USDC. darkdrop.app 6wKRRP1c2gkWESch723bmgCWiBYiYvn4krspZXdApump https://t.me/darkdrop_sol https://x.com/i/status/2058967111176015969
👏1
6wKRRP1c2gkWESch723bmgCWiBYiYvn4krspZXdApump usdc just landed on darkdrop
❤1
Got a good talk with some guys from different chain. They’re looking into DarkDrop right now, and we’ll see if they decide to support it. They’re still a bit indecisive since the USDC integration hasn’t been deployed yet. The main reason is that it’s not easy to just add test code into an already working codebase. It needs a lot of testing before deployment, and I can’t deploy it yet because of the Frontier judging.…
🔥1
Foundation done, the mint provisioning flow is complete. initialize_mint_config initialize_mint_trees initialize_mint_vault The next instruction create_drop_spl is the first user-facing one, actually moves USDC into the vault.
5 hours left on @colosseum frontier. $darkdrop has been months of building, 6 verified audits, late nights, and a lot of people who showed up when it mattered. Thank you to everyone who rode with us: The RPC teams, founders, and co-founders — @DIMIDJ of @Quicknode, @easeev of @ChainstackHQ, the whole team at @Alchemy especially @nikil, and @mert of @Helius. The judges who took our calls — @SuperteamSG, @superteam…
zellic_io / v12 sh is auditing $darkdrop repo/codes for securities, generates executable proof-of-concept exploits. v12 is an autonomous security with exploit-verified findings and automated patches. still on compile step after out of the queue I think its going to take a few hours. https://x.com/i/status/2053821478018470095
Showing the 12 most recent of 20 posts we hold for @Mr_H_calls. 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.
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.
@Mr_H_calls named 5 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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.
“Book Of Degens” (@Mr_H_calls), 200 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Mr_H_calls.
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.