Channel
@fusiondevelopersannouncement
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
61subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001285408314 |
|---|---|
| Type | Channel |
| Username | @fusiondevelopersannouncement |
| Created | Between 1 April 2018 and 20 July 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/fusiondevelopersannouncement |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 23:34 | 61 | -1 |
| 10 Aug 2026, 04:01 | 62 | no change |
| 7 Aug 2026, 21:11 | 62 | first reading |
20 posts held, back to 20 July 2019 — 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 5 December 2019. An engagement rate over an empty window would be a number about nothing.
Dear Fusionites, After discussion with our awesome OG community members, many of whom assisted in testing our Payable Staged Network (PSN). We have taken onboard feedback that hardware wallet users unfairly received time-locked rewards. If you were a hardware wallet user and believe your staking rewards from PSN were impacted, please follow the steps in this article! https://fusionnetworks.zendesk.com/hc/en-us/art…
Signed Yona T
Fusion open-sourced the highly anticipated DCRM 5.0 code, released a Developer Client and Boilerplate to expedite application builds on Fusion and continued final testing of exciting upcoming new features. Check it all out in Release Notes 3.7. https://fusionnetworks.zendesk.com/hc/en-us/articles/360039141494-Release-Notes-3-7
Signed Yona T
Just this morning, the Fusion Foundation distributed 468,750 FSN (time-locked for 3 months) to early adopters that earned time-locked rewards for staking on PSN. We thank PSN stakers for helping us deliver a robust MainNet that has run smoothly since going live on June 30.
Signed Yona T
Thanks to one of our most dedicated FOSC members @algoreee for this excellent article that helps developers get started building apps on Fusion. Alg is an accomplished person and consistent contributor to the Fusion communty, we we are grateful to have him. As part of the developer campaign bounties, Alg will be sent a 3K FSN time-lock for 3 months as a reward for the article 👏👏👏 https://medium.com/@hyperionxxx/int…
Signed Yona T
During sprint 3.6 the tech team began final testing of upcoming new features and made significant improvements to the Node Stats monitor and EZswap gateway. https://fusionnetworks.zendesk.com/hc/en-us/articles/360038901473-Release-Notes-3-6
Signed Yona T
Because relatively short notice was given to inform the staking community of the requirements to support the recent Fusion network hard fork, we have decided to subsidise nodes that failed to update in time with 5000 FSN time-locked for one month. https://medium.com/@fusionprotocol/fusion-foundation-to-give-subsidy-for-staking-nodes-that-failed-to-support-hard-fork-in-time-6ed14fd66512
Signed Yona T
Check out Release Notes 3.5 to see the Fusion application that received a substantial revamp, and the incredibly exciting new features that are set to be released in the very near future! https://fusionnetworks.zendesk.com/hc/en-us/articles/360037520894-Release-Notes-3-5
Signed Yona T
Reminder 🔊🔊 For those of you who have have joined the 2 Million FSN Open Source Community Campaign, we are reviewing submissions this week! Make sure you have provided all the relevant information requested in the Google form. Please remember that joining the github.com/fsn-dev public community is also required to earn your reward!
Signed Yona T
Everything you need to know about the upcoming MainNet upgrade 3.2 that implements: 1. Community voted ‘state change’ solution to the wallet theft. 2. Version 3.1 network upgrade already trialed on TestNet. 3. New block synching functionality. https://medium.com/@fusionprotocol/fusion-mainnet-3-2-upgrade-announcement-94b1e5a54d9c https://twitter.com/FUSIONProtocol/status/1184989004023947264
Signed Yona T
We are proud to announce that we have updated the following applications and services: - MyFUSIONWallet (Asia host as well) - Block Explorer - All of our API Servers Please check out the release notes here: https://fusionnetworks.zendesk.com/hc/en-us/articles/360036563074-Release-Notes-3-4
Signed Joey | Always check if I am @BitJoe
Fusion will upgrade its test network at block height 534,500, expected to arrive on Sunday the 29th of September. The upgrade involves expanding the functionality of the consensus code and adding to our API tool kit. https://medium.com/@fusionprotocol/fusion-test-network-upgrade-a7cf9334f8c0
Signed Yona T
Hi Fusionites, Just a reminder that the Fusion bug bounty is very much live and running. We recently made a slight change to to the submission process by requesting that bug hunters submit their bugs via a ticket on Zendesk rather than the email address that was previously provided. To learn more about the bug bounty, check out the link below! https://fusionnetworks.zendesk.com/hc/en-us/articles/360026344794-Bug-a…
Signed Yona T
Showing the 12 most recent of 20 posts we hold for @fusiondevelopersannouncement. 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.
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.
@fusiondevelopersannouncement 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.
References a handle that is not a live channel — we have no record it ever was one.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“FUSION Developers Announcements” (@fusiondevelopersannouncement), 61 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/fusiondevelopersannouncement.
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.