Telegram RegisterThe public register of Telegram

Channel

HackenProof - Crypto Bug Bounty

@hackenproof

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

712subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001726955006
TypeChannel
Username@hackenproof
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/hackenproof

Growth

712713712.57 Aug 2026, 00:47 — 713 subscribers7 Aug 2026, 20:11 — 712 subscribers7 Aug 2026, 00:477 Aug 2026, 20:11
2 measurements taken within a single day, net -1. 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 712–713 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 20:11712-1
7 Aug 2026, 00:47713first reading

Engagement

20 posts held, back to 21 May 2026the 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 · 30 days
49.4%
avg views ÷ 712 subscribers
Avg views / post
352
3 posts measured
Reaction rate
1.04%
reactions ÷ views · ER floor
Posts in window
3
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 July 2026
Posts held20 (21 May 202624 July 2026)
Views total1,055
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 00:47 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.

Reaction mix

72 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 44.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3244.4%
3143.1%
👍56.94%
💩22.78%
👎11.39%
😁11.39%

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 18 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 72reactions 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 21 May 2026 to 24 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.

Recent posts

24 Jul 2026, 09:01 UTC242 views3 reactionsread 7 August 2026
Photo

✅ [New bug bounty] ADI PredictStreet has been listed on HackenProof: The project rewards up to $10,000 per critical bug. ℹ️ About ADI PredictStreet: ADI PredictStreet is a licensed prediction market platform where users trade on the outcomes of real-world events. 💸 ADI PredictStreet bug bounty rewards hackers according to these tiers: - Critical: up to $10,000 - High: up to $5,000 Once you’re ready, click here

🔥3

20 Jul 2026, 14:33 UTC501 views4 reactionsread 7 August 2026
Photo

✅ [3 New DualDefense Contests] Push Chain has launched three new DualDefense Contests on HackenProof! - Reward pool: Up to $10,000 per contest - End date: August 3, 2026 - Last audit: By @hackenclub Scopes: 1️⃣ Push Chain SVM Gateway 2️⃣ Push Chain Core Contracts 3️⃣ Push Chain EVM Gateway Join the contests now!

🔥3👍1

16 Jul 2026, 12:00 UTC312 views4 reactionsread 7 August 2026
Photo

✅ [New bug bounty] StarkWare has launched 3 programs on HackenProof. Security researchers can now hunt across: 1. Starknet Web & Smart Contracts 2. Starknet Staking 3. Starknet Blockchain / DLT The programs reward hackers up to $250,000 per critical bug. ℹ️ About Starkware: StarkWare is a blockchain infrastructure company developing STARK-based scaling solutions, including StarkEx and Starknet, to make blockcha

🔥4

13 Jul 2026, 14:12 UTC574 views7 reactionsread 7 August 2026
Photo

✅ [New DualDefense Contest] A fresh challenge just dropped on HackenProof! The DualDefense Contest with Push Chain is now live. - Reward pool: up to $70,000 - End Date: August 2, 2026 - Scope: Push Chain L1 codebase - Last Audit: by @hackenclub Join the contest now!

🔥61

8 Jul 2026, 17:04 UTC322 views2 reactionsread 7 August 2026
Photo

✅ [New DualDefense Contest] A fresh challenge just dropped on HackenProof! The DualDefense Contest with Telcoin is now live. - Reward pool: Up to $3,200 - End Date: 22 July, 2026 - Scope: Smart contract - Last Audit: by @hackenclub Join the contest now!

2

6 Jul 2026, 12:38 UTC321 views3 reactionsread 7 August 2026
Photo

✅ [New bug bounty] Zynk has been listed on HackenProof: The project rewards up to $5,000 per critical bug. ℹ️ About Zynk: Zynk is a global payments infrastructure platform powering instant cross-border settlements and money transfers for remittance companies, neo-banks, and payment service providers. Once you’re ready, click here to join the bounty hunt! #new_bounty

🔥3

16 Jun 2026, 18:15 UTC513 views4 reactionsread 7 August 2026
Photo

✅ [New DualDefense Contest] A fresh challenge just dropped on HackenProof! The DualDefense Contest with DART’s is now live. - Reward pool: Up to $3,000 - End Date: June 30, 2026 - Scope: Smart contract - Last Audit: by @hackenclub Join the contest now!

👍31

11 Jun 2026, 13:01 UTC471 views1 reactionsread 7 August 2026
Photo

✅ Good news from Bitkub Group New web assets have been added to their bug bounty program on HackenProof. ℹ️ About Bitkub: Bitkub Capital Group Holdings Co., Ltd. is building the digital economic infrastructure of tomorrow and connecting the traditional world with the digital world. Once you’re ready, click here to join the bounty hunt!

🔥1

9 Jun 2026, 14:14 UTC392 views9 reactionsread 7 August 2026
Photo

✅ [New DualDefense Contest] A fresh challenge just dropped on HackenProof! The DualDefense Contest with Tokenize.it is now live. - Reward pool: Up to $5,000 - End Date: June 27, 2026 - Scope: Smart contract - Last Audit: by @hackenclub Join the contest now!

6💩2👎1

5 Jun 2026, 13:41 UTC371 views5 reactionsread 7 August 2026
Photo

✅ [New Audit Contest] @TipRunAlpha Smart Contract Audit Contest is LIVE on HackenProof! TipRun is a cricket-focused prediction market exchange — and now it’s your turn to test it! 💰 Reward pool: Up to $15,000 📅 Duration: June 5 - June 24 → Join the contest now!

5

4 Jun 2026, 16:34 UTC299 views3 reactionsread 7 August 2026
Photo

✅ [New DualDefense Contest] A fresh challenge just dropped on HackenProof! The DualDefense Contest with Neyro network is now live. - Reward pool: Up to $4,000 - End Date: June 9, 2026 - Scope: Smart contract - Last Audit: by @hackenclub Join the contest now!

3

4 Jun 2026, 16:26 UTC269 views6 reactionsread 7 August 2026
Photo

✅ [New Audit Contest] 0xMarkets Smart Contract Audit Contest is LIVE on HackenProof! 0xMarkets is a multi-asset perpetual futures DEX for FX, crypto, and commodities, powered by Bittensor and built on the Cartha Subnet. Now it’s your turn to test it! 💰 Reward pool: Up to $30,000 📅 Duration: June 4 – July 8 👉 Join the contest now!

🔥42

Showing the 12 most recent of 20 posts we hold for @hackenproof. 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

Citation-graph rank — 364,187 of 1,169,250entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 1 registered channel — 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.

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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“HackenProof - Crypto Bug Bounty” (@hackenproof), 712 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/hackenproof.

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.