Channel
@DuskAnnouncements
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,793subscribers
-18 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001156481225 |
|---|---|
| Type | Channel |
| Username | @DuskAnnouncements |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/DuskAnnouncements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 19:44 | 1,793 | -2 |
| 23 Aug 2026, 02:57 | 1,795 | -2 |
| 19 Aug 2026, 18:42 | 1,797 | -4 |
| 16 Aug 2026, 22:23 | 1,801 | -3 |
| 13 Aug 2026, 12:38 | 1,804 | -4 |
| 10 Aug 2026, 03:20 | 1,808 | -2 |
| 6 Aug 2026, 23:20 | 1,810 | -1 |
| 6 Aug 2026, 06:50 | 1,811 | no change |
| 6 Aug 2026, 04:13 | 1,811 | first reading |
20 posts held, back to 7 October 2024 — 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 pagesof 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 24 October 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
🚨 Important Update 🚨 Hey everyone! Moving forward, we will no longer be using this channel for announcements. To make things easier to navigate and keep all the information in one place, all future announcements will be posted in our main Telegram group. 📢 This will be the last announcement in this channel. If you haven’t done so already, join our main group here: https://t.me/DuskNetwork How to Enable Notificatio…
NOCTURNE UPDATE Piecrust Optimizations We have been continuing our work on Piecrust optimzations, which focus on scalability and maintaining good performance when high numbers of smart contracts are deployed so that as overall state size grows, performance does not degrade. There are two sides to this, one thing is a good performance per se, which is also being improved, and the other is minimising the dependency o…
NOCTURNE UPDATE The reset went well, and is live and producing blocks 💪 This reset brings with it updates and optimizations which we are pleased about and are working as predicted. Additionally, stake operations (stake/unstake/withdraw) now cost 10 times less. That's all today, and see you tomorrow!
Hey guys! Friendly reminder for all node operators on Nocturne: This update requires a reset. If you're already running a node, follow the instructions here before tomorrow morning 10 AM CEST: https://docs.dusk.network/operator/nocturne/upgrade-node#nocturne-reset If you haven't set up a Nocturne node yet and want to participate, you can follow the guide here: https://docs.dusk.network/operator/nocturne/node-runnin…
NOCTURNE UPDATE Happy Monday everyone! We have quite a few updates for you today. Nocturne Reset We will be resetting Nocturne tomorrow morning. The timeline is as follows: 16h We will prep the installer for the update 18h We will make the installer available (around this time, not necessarily bang onthe dot) 9h tomorrow the reset will take effect and begin producing new blocks Please see the docs for instructions…
📢 Discord Revamp Announcement 📢 Hey everyone! 👋🏻 We’ve made some exciting updates to our Discord to make it more organized and engaging for the entire community. Here’s what’s new: 🎉 Community Rewards: By engaging with content, participating in events, and interacting with the community, you can now earn points and unlock exclusive rewards! Head over to #engage on Discord to get started. 🎟 New Ticketing System: H…
NOCTURNE UPDATE I don't have that much to report today, just that everything is going well and we are continuing to optimize and improve the network. We expect this PR to be merged soon https://github.com/dusk-network/rusk/pull/2475 and when it is it will further reduce the probability of losing synchrony with the rest of the network, so look out for this soon! Thank you to everyone who attended and asked question…
@everyone NOCTURNE UPDATE Consensus Improvement This update makes the consensus much more robust by shortcircuiting the iteration when a Quorum other than Valid (like Invalid Quorum or No Candidate Quorum ) is reached. This is the PR https://github.com/dusk-network/rusk/pull/2633 And it solves this issue https://github.com/dusk-network/rusk/issues/2301 AMA Don’t forget to join us later today for the AMA with Fulv…
NOCTURNE UPDATE Welcome to another update! New node installer version You only need to follow the upgrade instructions: https://docs.dusk.network/operator/nocturne/upgrade-node#how-to-upgrade This is not a mandatory release. It fixes a configuration problem with Rusk wallet, fixes the Moonlight unstake operation and stake information provides more information. Network stability improvement Nodes now take into co…
NOCTURNE UPDATE We have three main things for you today.. 1. Public docs Our docs are are now public, allowing anyone to open issues, create PRs, and contribute to our documentation. This furthers our commitment to transparency and decentralization within the Dusk ecosystem. We're inviting the community to help keep our docs accurate, relevant, and useful. So check it out and get involved! LINK: https://github.co…
We are pleased to share the Migration Contract Audit Report, performed by Zellic 💪 The report was very positive, finding 0 issues (yes, zero!) and we are pleased to continue driving forward to deliver mainnet. Check out the report below 👇 https://dusk.network/news/migration-contract-audit/
NOCTURNE UPDATE Over the weekend Nocturne has been ticking like a clock, so is looking good in that regard. We also onboarded 50+ nodes that are not ours, so this is great for decentralization and seeing how different nodes and set ups perform. Overall not too much to report, just that we are making good and constant progress and Nocturne is performing well.
Showing the 12 most recent of 20 posts we hold for @DuskAnnouncements. 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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“Dusk - Announcement Channel” (@DuskAnnouncements), 1,793 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/DuskAnnouncements.
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.