Compete to win up to $5000 in USDC and Forta NFTs by building a Forta Agent! Starting NOW! Take part here: https://docs.forta.network/en/latest/contest3-oz/ OpenZeppelin has provided two sets of agent requirements to address the security needs of their smart contracts library. Any agent developer may take part in this contest by creating and publishing an open-source agent that meets the requirements of either chal…

Channel
FortaProtocol
@FortaProtocol
On this record: Topic · Growth · Engagement · Posts · Cite this entry
275subscribers
-2 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 | -1001324289483 |
|---|---|
| Type | Channel |
| Username | @FortaProtocol |
| Created | 1 October 2021 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 10 October 2026 |
| On Telegram | t.me/FortaProtocol |
Topic
Hacking & security — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 23:19 | 275 | -2 |
| 7 Aug 2026, 01:32 | 277 | no change |
| 7 Aug 2026, 01:19 | 277 | first reading |
Engagement
9 posts held, back to 1 October 2021 — 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 page 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 9 posts for this entry, the most recent from 18 November 2021. An engagement rate over an empty window would be a number about nothing.
Recent posts
Forta in action: check out how Forta could have prevented Poly Network’s $600M hack at https://forta.org/poly-network-hack/
Compete to win up to $7500 in COMP and Forta NFT’s by building a Forta Agent! Starting TODAY!! Take part here: https://docs.forta.network/en/latest/contest1/ Compound Grants has provided five sets of agent requirements to meet the security needs of the Compound Protocol. Any agent developer may take part in this contest by creating and publishing an open-source agent that meets the requirements of any of the five c…
Meeting demands of growth & moving to Polygon Great news Forta devs and users! The community is growing faster than we expected and to keep up with the overwhelming demand we began migrating all Forta smart contracts from Goerli to Polygon today at 12:00 UTC. This will provide the infrastructure needed to add horizontal node scaling, a new assigner with registry listing, in addition to an enhanced smart contract pr…
Tomasz Stańczak of Nethermind discusses the security needs of Web3, and why Forta is vital to securing their development ecosystem https://forta.org/nethermind-eth-heartbeat/
Welcome to the Official Forta Telegram!
Channel photo updated
Channel photo updated
Channel created
Showing the 9 most recent of 9 posts we hold for @FortaProtocol. 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“FortaProtocol” (@FortaProtocol), 275 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/FortaProtocol.
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.