Forest Protocol is moving fast🌲 A lot has landed recently. 🪪 Usernames live on Forest ⛓️ 200+ wallets integrated 🎮 New community games with +200 players 🔒 40% of $FOREST market cap staked The ecosystem keeps expanding. https://x.com/ProtocolForest/status/2076932543723589864?s=20

Channel
Forest Announcements
@Forest_Announcements
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
434subscribers
-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 | -1003801535365 |
|---|---|
| Type | Channel |
| Username | @Forest_Announcements |
| Created | Between 1 February 2026 and 1 June 2026— 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 | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/Forest_Announcements |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 13:52 | 434 | -2 |
| 8 Aug 2026, 05:16 | 436 | no change |
| 7 Aug 2026, 19:22 | 436 | first reading |
Engagement
20 posts held, back to 1 June 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 14 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
7 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 3 | 42.9% | |
| ❤ | 2 | 28.6% | |
| 👌 | 2 | 28.6% |
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 6 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 7reactions 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 1 June 2026 to 14 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
The proven infrastructure behind @ZeeverseGame, one of Web3's most developed game economies, is now open to every builder on @BNBChain🌲 Got a game idea? Build it, integrate Forest Playkit, and your game is on-chain with a full token economy from day one. No smart contracts. No backend. The GameFi2.0 infrastructure is live👀 Details 👇 https://forest.inc/news/forest-playkit-infrastructure-behind-zeeverse-economy h…
More builders shipping on Forest Protocol🌲 IRONVEIN is just deployed powered by Playkit - a new on-chain game with a full token economy. The ecosystem keeps growing and the infrastructure is open to every builder 👀 Play now 👇 https://forest.inc/token/39261bb6-4c63-4bbc-82dc-322c292e87a7 https://x.com/ProtocolForest/status/2072576928033243495?s=20
Introducing: Games of the Week🌲 Forest is filling up with new games with different genres, mechanics, all with token economies and rewards powered by Forest Playkit. This week: 🕷 Spider 🚀 Defender 🍓 Forest Garden 🐛 Wurm 345+ players across new games this week alone. Explore and play 👇 Spider Card ($SPDR): The first rewarding solitaire game on Forest Protocol. Win hands, earn tokens: https://forest.inc/token/4e62…
Last 24 hours of the $DOORZ Trading Competition🚨 250K Seeds reward pool. Every buy and sell counts. Play the game to earn more $DOORZ, then trade it to climb higher. Seeds convert to $FOREST rewards in Seed Vault. 🌱 Links 👇 Leaderboard: https://forest.inc/leaderboard Trade & play: https://forest.inc/token/fb72e91c-14e9-487d-bc90-6fea206afbbb https://x.com/ProtocolForest/status/2072205797057073330?s=20
DOORZ by @Acid_Labz just dropped. The first of several Playkit games lined up🌲 $FOREST stakers were airdropped 1M tokens. In Forest Economy, staking always comes with a head start. $DOORZ Trading Competition is also on with 250K Seeds. Trade your airdrop or play and earn👇 https://x.com/ProtocolForest/status/2071491170794922324?s=20
The agentic era is rolling out🤖🌲 Forest Playkit is now on GitHub as an AI skill. For the first time, any agent can deploy an on-chain game economy. No smart contracts, no backend. The first step toward agents building and playing on Forest Protocol autonomously👀 Details👇 Docs 👉https://forest.inc/docs/developers/ai-skill Github👉https://github.com/Forest-Protocol/forest-skills What is Playkit 👉https://forest.inc/n…
Forest Builder is live🌲 Already receiving a ton of feedback. Builder V2 is dropping soon. Feedback to deployment in days with a better and more advanced version. Try it and share your thoughts. Join the community👇 Builder👉 https://forest.inc/builder Discord👉 https://discord.gg/NnHk3hfTmZ Telegram👉 https://t.me/ProtocolForest https://x.com/ProtocolForest/status/2067215457409479034?s=20
❤1
New Forest Docs are live🌲 → Developer handbook → Creator playbook → Forest Playkit, Builder, Cloud, Agentic Layer → The vision Everything you need to build and understand where Forest Protocol is headed. This is where the next phase starts. https://forest.inc/docs https://x.com/ProtocolForest/status/2067144998030602325?s=20
Forest Builder is live🌲 For the first time on @BNBCHAIN, idea to on-chain app. In minutes. It's always Day 1 with Forest Protocol. Build. Explore. Share feedback as we roll out the agentic economy. Early builders and contributors will be rewarded as always. Builder: https://forest.inc/builder Details: https://forest.inc/news/forest-builder-imagine-describe-deploy-on-chain https://x.com/ProtocolForest/status/2066…
Building using Forest Builder will have perks🌲 Early users get a Builder Badge. Builder Badge = always eligible for future airdrops. Read more: https://forest.inc/news/forest-builder-imagine-describe-deploy-on-chain https://x.com/ProtocolForest/status/2066799168291537051?s=20
Staking and holding $FOREST always pays off at Forest Protocol🌲 💰$36K+ in rewards distributed 📈100% APY 🌱Seeds earned with every stake Airdrops and rewards are a constant. Every layer of Forest Economy is designed to reward ecosystem participants. https://x.com/ProtocolForest/status/2066413906604474583?s=20 Recent history 👇 Staking upside for contributors: https://x.com/ProtocolForest/status/2066413908932321429?s…
Showing the 12 most recent of 20 posts we hold for @Forest_Announcements. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@Forest_Announcements named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 9 August 2026 – 9 August 2026
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Forest Announcements” (@Forest_Announcements), 434 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Forest_Announcements.
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.