https://youtu.be/dqNdTqAOx6M?si=kCA88g7b1tfzOeIh https://x.com/rektoff_xyz/status/1752018024054370361?s=46
🔥7❤4

Channel
@rektoff
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,614subscribers
-42 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001810411574 |
|---|---|
| Type | Channel |
| Username | @rektoff |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/rektoff |
Technology — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 21:55 | 1,614 | -1 |
| 5 Oct 2026, 00:40 | 1,615 | -7 |
| 25 Sept 2026, 23:17 | 1,622 | -5 |
| 15 Sept 2026, 05:58 | 1,627 | -2 |
| 11 Sept 2026, 23:55 | 1,629 | -2 |
| 7 Sept 2026, 21:17 | 1,631 | -3 |
| 2 Sept 2026, 12:57 | 1,634 | +1 |
| 30 Aug 2026, 23:04 | 1,633 | -1 |
| 27 Aug 2026, 19:28 | 1,634 | -1 |
| 24 Aug 2026, 17:49 | 1,635 | -7 |
| 20 Aug 2026, 15:33 | 1,642 | -6 |
| 17 Aug 2026, 16:57 | 1,648 | -2 |
| 14 Aug 2026, 00:54 | 1,650 | -3 |
| 10 Aug 2026, 22:01 | 1,653 | -3 |
| 7 Aug 2026, 17:38 | 1,656 | no change |
| 7 Aug 2026, 10:16 | 1,656 | first reading |
20 posts held, back to 30 November 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 29 January 2024. An engagement rate over an empty window would be a number about nothing.
138 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 63.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 87 | 63.0% | |
| ❤ | 32 | 23.2% | |
| 👍 | 16 | 11.6% | |
| ❤🔥 | 2 | 1.45% | |
| 🥰 | 1 | 0.725% |
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 20 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 138 reactions 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 30 November 2023 to 29 January 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://youtu.be/dqNdTqAOx6M?si=kCA88g7b1tfzOeIh https://x.com/rektoff_xyz/status/1752018024054370361?s=46
🔥7❤4
happy Friday rektoffians! If you are looking to learn more about Rektoff and want to check some great articles / repos / workshops on Rust security - check out our Notion welcome page 👨🍳 https://rektoff.notion.site/Rektoff-06d59fbfbb29429693486e25748baa76?pvs=4
🔥4❤🔥2
Looking for a good weekend read on Rust security? Just google “rust web3/blockchain security” and open up the first article. You will like it 🖤
❤6
We are scaling the magnitude of security solutions and knowledge through our recent network collaboration with SunSec and DefiHackLabs! Check them out: Github - https://github.com/SunWeb3Sec/DeFiHackLabs Notion Page - https://web3sec.notion.site/I-m-SunSec-ddaa8bf9a985494dbaf70d698345b899 Discord community - https://discord.com/invite/Fjyngakf3h
🔥5❤2
We are glad to opensource our holistic security strategy for Solana dev teams. Here is a Systematic Security Roadmap for a full lifecycle of Solana applications. https://github.com/Rektoff/Security-Roadmap-for-Solana-applications https://x.com/rektoff_xyz/status/1744771734782263613?s=20
👍5🔥5❤1
2024 is here! We want to say a huge thank you to everyone who has supported us from the start until this day. We have made great progress as an industry and will continue to accelerate blockchain security systems next year! Spend time with your family and take the deepest naps that you've ever had before diving back into holistic web3 security. Happy holidays, fam! We'll be back soon. Stay safe. Stay rektoff. htt…
❤6🔥4🥰1
Hacker spotlight interview with our internal expert @yhtyyar_s, who successfully secured his first 100k bounty.⤵️ https://x.com/rektoff_xyz/status/1740103991986438178?s=46
🔥8
2024 is all about DevSecOps, security primitives and Rust lang in the blockchain industry. https://x.com/rektoff_xyz/status/1738161367213871426?s=46
🔥4
We published our first workshop related to “AI in Blockchain security” week. Advanced Fuzzing and LLM integrations into Security Practices by @privateqi from fuzz.land team. Go, check it out! https://www.youtube.com/embed/NOLL4nx9Xnc https://x.com/rektoff_xyz/status/1737843692856369621?s=46
🔥6
straightforward mandated shilling of EVM smart contract toolkit written in Rust! https://x.com/rektoff_xyz/status/1737554038709756298?s=46
🔥3👍2
Our expertise centers on EVM-based applications and DeFi protocols specifically. However, our key and unique specialties are in Rust-specific/Non-EVM protocols, based on the skills and experience of our onboarded units from the Rektoff community. — Request a spot for a security review and begin building your security system from a measurable result. https://x.com/rektoff_xyz/status/1736713321158521301?s=46
🔥4👍2
XSS vuln. https://x.com/rektoff_xyz/status/1734884777134531029?s=46
👍2
Showing the 12 most recent of 20 posts we hold for @rektoff. 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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“Rektoff” (@rektoff), 1,614 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/rektoff.
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.