Channel
@PositiveWeb3
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
130subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001620019916 |
|---|---|
| Type | Channel |
| Username | @PositiveWeb3 |
| Description | Web3 Security Research audit@positive.com x.com/PositiveWeb3 GitHub.com/PositiveSecurity |
| Created | 26 September 2023 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/PositiveWeb3 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 01:16 | 130 | no change |
| 7 Aug 2026, 16:03 | 130 | first reading |
15 posts held, back to 26 September 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 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 15 posts for this entry, the most recent from 24 May 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
136 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 40.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 55 | 40.4% | |
| 👍 | 53 | 39.0% | |
| ❤ | 13 | 9.56% | |
| 👏 | 8 | 5.88% | |
| 🙏 | 4 | 2.94% | |
| ❤🔥 | 2 | 1.47% | |
| 👎 | 1 | 0.735% |
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 13 of the 15 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 136reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 26 September 2023 to 24 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Bugged Blockchain Challenge is LIVE! 🔥 A deliberately vulnerable blockchain awaits your hacking skills! Break into the node or wallet, and submit your top exploit report for a chance to win a massive 100 TON bounty! Full details at positive.com/bounties.
🔥8❤1👎1👏1
We’ve launched the ultimate hunt for bugs and hacker mastery — the epic CTF has begun at positive.com/ctf! On the menu: blazing challenges in EVM and TON security — plus one juicy Bug Bounty worth 100 TON!
🔥11👍4👏1
Discover TONGraph, a Visual Studio code extension that brings clarity to TON smart contract research by visualizing function call graphs in FunC, Tact, and Tolk. Developed by @PositiveWeb3 security researchers, we invite you to try it out and share your feedback. #TONGraph #TON https://marketplace.visualstudio.com/items?itemName=PositiveWeb3.ton-graph https://github.com/PositiveSecurity/ton-graph
👍7🔥4❤3
🎉 Check out this mind-blowing longread on hacking Web3 AI agents. 🤖 Uncover the secrets of the digital frontier! https://blog.positive.com/security-of-ai-agents-in-web3-dbcb371544f7
👍6❤3🔥3
Unleash security mode on your TON smart contracts! 🚀 Our cutting-edge research exposes deadly pitfalls & hidden hacks that can torch your tokens. Level up your blockchain game—read the ultimate guide now 👉 https://blog.positive.com/security-audit-of-smart-contracts-in-ton-key-mistakes-and-tips-33ff3502cfd7 #TON #SmartContracts #Blockchain
👍6🔥3❤1
#update The "update v2" commit makes changes to the README.md file of the TON smart contract audit guide (https://github.com/PositiveSecurity/ton-audit-guide), with the main points summarized as follows: Restructuring Security Recommendations: - Updated guidelines on operation independence, using the carry-value pattern, protection against replay attacks, and proper flag handling. Enhancing Message Formation and G…
👍4🔥3👏1
🚀 Next-gen security for TON smart contracts! Meet our #AI-powered RAG agent, built on #ChatGPT. It helps audit, looks for vulnerabilities, and is built to strengthen Web3 security. Welcome to the future of security @ton_blockchain https://chatgpt.com/g/g-677ef5283be881918960cb5a76e1dd47-ton-agent-by-positiveweb3
👍4❤🔥2🔥2🙏1
New #Web3Security Conf 😎 🚀 Call for Papers is Open! 🎉 We pay for flight and lodging for speakers! Join us at Positive Hack Days 2025 in Luzhniki, Moscow – the biggest cybersecurity event! 📅 May 22-24, 2025 🔹 Hardcore Web3 security talks from top experts 🔹 A truly global, multicultural conference on Web3 security 🔹 CTF competition focused on #Web3 challenges 🔹 Part of the largest cybersecurity festival – #PHDays …
👍5🔥3❤1
Formal verification of #Solidity smart contracts in the #ConCert framework. https://blog.positive.com/formal-verification-of-smart-contracts-in-the-concert-framework-e04ce79ddc09 #coq #web3 #web3security
👍3🔥3🙏3👏1
How We Trained an #LLM to Find Vulnerabilities in #Solidity Smart Contracts https://blog.positive.com/how-we-trained-an-llm-to-find-vulnerabilities-in-solidity-smart-contracts-9337bcae5e46
👍8🔥4👏3
#TON project audit checklist https://github.com/PositiveSecurity/ton-audit-guide
👍4🔥3❤1
#ZKP audit checklist: https://github.com/PositiveSecurity/zk-audit-guide
🔥4❤3👍1
Showing the 12 most recent of 15 posts we hold for @PositiveWeb3. 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 — 348,913 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.
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.
Named by 2 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Positive Web3” (@PositiveWeb3), 130 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/PositiveWeb3.
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.