Team,
2 Months after the proposal passed.
When this will finally be implemented?
What is the update?
Work on some of the involved contracts is progressing, from what I understand. Once that’s done; an audit of the changes, and then it should be ready to deploy.
1 Like
Thanks for the update Jonezee.
A community member voicing dissatisfaction with development or governance progress has been a reoccurring event.
I think the underlying issue is a lack of transparency between the core developers and the community. From the outside it might seem like nothing is happening.
It would be outrageous to expect the team to maintain a public scrum board, but publishing a very brief roadmap that extended a few weeks into the future would allow the community to have realistic expectations about development times and team priorities.
This could be as simple as a weekly discord post, with a sentence or two describing the goals of the team for each week, extending 4-8 weeks into the future. This way, when a proposal passes, the community can see its development progress, form realistic timeline expectations and make governance decisions that are more conscious of developer resources.
The second issue I notice regards uncertainty about progressing from this forum to a snapshot vote. I don’t have any suggestions and I not sure anything needs to change, but formalizing the mechanism in writing might alleviate some confusion.
I dont mean to hijack this thread with a different discussion, but I felt something needed to be said.
There are development updates happening every Friday which includes the past activities ‘big’ of the week.
The current activites are mainly shown in the current governance votes and in these weekly updates. When something concrete has been finished it will always be mentioned in these updates.
e.g. when Buyback and Distribute has been coded fully and is in audit, it will be mentioned in the development updates. I don’t think we need to focus to much on all small changes that are happening until the main things are finished, and for a legal perspective we cannot say too much of what’s happening for obvious reasons.
I see that they’re also posted on the Twitter now on Mondays x.com
3 Likes
Appreciate the response, Sands.
A lot is actively being shared in terms of development achievements. Let me list how, for those who feel like they’re missing out on this info:
- There’s a weekly Development Update segment in every news announcement on Friday. This goes out on TG as well as in the GMX Discord via the Announcement channels.
Ex: Telegram: Contact @GMX_Announcements
- And there’s a separate, longer development summary GMX publishes roughly every month on all social channels. For example:
That said, I understand the desire for a brief update that explains dev priorities for the coming weeks/months. From what I understand, this is hampered by the potential legal difficulties associated with future-facing dev pronouncements. Any ‘promise’ of upcoming functionality is risky. Talking about work that has been completed, that is fine.
What is currently being prioritised, can generally be gathered from the Snapshot votes: Snapshot
Roadmaps, though, are ambiguous in this regard. Is a roadmap a promise of what will be achieved, or just a guidepost for what devs would like to work on? Either way, the contributors are currently discussing how to share more of this vision for the future with the community. Please stay tuned.
3 Likes
Team, what is the update?
Here’s a status update:
- GMX Development
• The audit for the updated RewardRouterV2 to support rewards in the GMX token is scheduled to complete today, the updated RewardRouterV2 contract should be deployed next week
• The code for the contract to buyback GMX has been completed, the audit for it will begin in the coming week
4 Likes
Great news, thanks for an update.