The Midgard protocol repository shows plenty of activity with regular commits, but there's a real gap between what's visible in the code and what actually matters to the community—a clear project roadmap, current development priorities, and what's been shipped recently. It'd be helpful if the team could break down: what's in active development right now, what milestones were hit last cycle, and where things are headed next. Beyond Midgard, this kind of transparency issue isn't unique. A lot of projects struggle to translate technical progress into digestible updates for their community. Clear communication around development cycles, blockers, and delivery timelines would go a long way.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
9 Likes
Reward
9
5
Repost
Share
Comment
0/400
governance_lurker
· 01-11 16:50
Code activity indeed does not equal transparency; this point hits the pain points of too many projects.
View OriginalReply0
gas_fee_trauma
· 01-11 16:50
No matter how much code you pile up, it's useless if you don't tell us what you actually did.
View OriginalReply0
GasFeeTherapist
· 01-11 16:47
Exactly right, having more commits doesn't really mean much; the key is to let the community know what has actually been done.
View OriginalReply0
SandwichVictim
· 01-11 16:29
NGL, this is a common problem in Web3 projects. The code is active, but the community knows nothing.
View OriginalReply0
BlockchainFries
· 01-11 16:28
Code gets committed every day, but the community is still clueless. Isn't this just the norm in Web3? Haha
The Midgard protocol repository shows plenty of activity with regular commits, but there's a real gap between what's visible in the code and what actually matters to the community—a clear project roadmap, current development priorities, and what's been shipped recently. It'd be helpful if the team could break down: what's in active development right now, what milestones were hit last cycle, and where things are headed next. Beyond Midgard, this kind of transparency issue isn't unique. A lot of projects struggle to translate technical progress into digestible updates for their community. Clear communication around development cycles, blockers, and delivery timelines would go a long way.