I noticed that the team stopped giving ETAs. Finally! But I am missing a strategy to keep the community aligned when there are no ETAs. Recently, the updates on progress have been really lacking. It feels very shallow: we’re ready on our end.. there needs to be way more focus in community alignment by providing real updates on progress, also re implementation by partners. This relates to both discord/forum but also X. The X posts come accross as shallow marketing statements on repeat. They hardly provide actual information on progress. I also very much advise the Dusk account to start engaging more in discussions on real rwa.
7 Likes
Hey JDR, thanks for taking the time to put this together.
Indeed, not giving ETAs creates a new challenge. How do we keep the community meaningfully aligned and updated when we can’t give exact timelines?
Right now, the roadmap gives a high-level view of what we’re building and the stage each component is in. To complement that, we’ve been doing monthly updates through AMAs or written posts to share progress across development, partnerships, and ecosystem initiatives.
In some cases, once a feature or product is ready on our side, there can be a long lead time before it goes live, especially when working with regulated partners. That makes it tricky to give regular updates without repeating ourselves, but we’ll think about how to better surface what’s happening behind the scenes.
Would love to brainstorm with the community here, maybe that means more dev-focused updates, or deeper dives into understanding how processes or partner integrations work. Open to ideas!
On the X side, what kind of posts would you personally find more valuable or engaging? More technical breakdowns? RWA market analysis?
I think the team can be much more clear and detailed in what is needed before implementation will actually take place, at an individual case level. A general remark like “this can take a while” simply does not create any alignment. I know there is a lot of information to be shared, but for some reason the team has decided that it is better not to share this.
I think clarity on this is especially needed when the announcements are piling up, but the actual implementation is still at zero.
As for the X posts, I feel they should also contain the above updates. And I feel that the Dusk account needs to spend a lot of time searching for relevant RWA posts and becoming part of the discussion, instead of merely dropping unilateral phrases on repeat. I know it takes a lot of time to do this right, but to me it is definitely worth it. And much more valuable than spending time spinning a wheel to reward bot-like responses under Dusk posts that have hardly any impact.
2 Likes
I fully align with this message. One of the main issues with the recent updates is that they’ve focused mainly on the public repository, while providing little to no information about the broader roadmap deliverables. Great to see DuskPay, Hyperstaking, and the “yet to be announced” Chainlink partnership, but there’s been a noticeable lack of recent updates on Zedger, Lightspeed, NPEX, and other key components — especially since previous announcements have yet to go live.
The communication around progress has felt increasingly shallow — we often hear that “we’re ready on our end,” but there’s not enough clarity on actual implementation, particularly from partners.
3 Likes
actually it feels like the monthly dusk update has disappeared after mainnet launch. That was one of the better parts of getting update on progess.
1 Like
Thanks for the thoughtful reply — it really helps frame the communication challenge from the team’s side.
I fully understand how not providing ETAs (especially when progress is gated by external, regulated partners) can make it difficult to share consistent updates. Even with AMAs, if there’s nothing new to disclose, it puts pressure on the team to repeat or overextend. I also recall that compiling technical updates, can be time-consuming — maybe there’s a lighter way to present them?
Besides from audio AMA, I would love to see more updates, even brief posts that highlight specific progress — like a little milestone within Zedger — could go a long way in keeping the community energized and aligned. A small but real win still builds momentum.
On the X side, I personally enjoy seeing data-driven breakdowns — for example, how much institutions currently spend on legacy infrastructure (rails, post-trade ops, etc). Defining the problem with concrete examples can make Dusk’s solution feel more tangible and urgent, especially as we approach launching Zedger. Without that, repeating the solution might start to lose impact.
Also, would love to hear more from the business side of the team — past research, market insights, or even internal debates around design choices. That perspective can deepen community appreciation for what’s being built, even before products go live.
Looking forward to seeing more progress & transparency. It makes a big difference.
2 Likes
I agree with the small updates but at the same time I think we need to at least keep in mind that work like Zedger is still in a private repository. So I hope the team can gives us as much as they are able to share publicly without endangering the development and “safety” of Zedger.
I think the example you give for data-driven breakdowns is amazing and it’s one of those things I always imagined would go a long way but I never really could formulate it like that.
1 Like
Thank you everyone for the suggestions!
Will review and see how we can implement better updates going forward.
Is it an idea to create a milestone dashboard where the different points of the roadmap are displayed with the progress that has been made? This way you can easily and clearly show where Dusk currently stands. Progress can be in percentages or per sub point. This can be displayed on the forum and the website. There are many examples of this and I have always found this to be a useful tool to make progress visible.
1 Like