As we step into the new year, we want to thank everyone for your support. Your involvement means so much to us!
This thread will serve as our hub for updating the ENS DAO. Here, we’ll share proposal results, governance-related metrics, and exciting developments as we continue our mission to make governance data more accessible.
We hope these updates will keep you informed, spark meaningful discussions, and pique your interest in exploring what Dhive has to offer.
We’re also opening this space for your feedback and suggestions! We’re always open to hear your thoughts and improve our project to better serve the community.
Let’s make 2025 a great year filled with success, collaboration, and good governance!
Happy to announce that Dhive has leveled up and would like to share with the community our new and exciting features:
⟐ Token holdings data is now available.
⟐ New governance metrics on profiles.
⟐ New and improved analytics dashboard for daos.
⟐ Proposals have a timeline for the voting cycle.
⟐ Charts can now be downloaded.
⟐ Profile identities support Base and Linea subdomains.
⟐ UI/UX improvements and performance optimization.
We invite you to take a moment to explore these features on dhive.io and share with us your thoughts and feedback.
Excited to share a new addition to our voting visualizations - an interactive chart to explore Copeland voting outcomes!
It was challenging to solve, but we stuck to our core principles of clear, clean, and traceable charts which guide all of our data visualizations.
And here’s our solution:
⟐ Pairwise comparison chart showing how each option scores in head-to-head matchups
⟐ Final scores are marked to highlight how they are calculated across all comparisons
⟐ Viewable votes distribution of any matchup by clicking on the score to reveal it
⟐ Designed to complement platforms where scores are shown but the logic behind them isn’t
Thanks for building this out - always beeen a fan of the interesting visuals by you guys.
Drop me or one of the Metagov stewards (@5pence.eth@daostrat.eth@netto.eth) a message with your Telegram - there is an ongoing discussion about the changes to the SP program proposed here:
One of us will add you to the conversation.
@netto.eth has created an interface he’s just shared:
This is one of the downsides of closed (albeit accessible) conversations - it makes it hard for passionate and capable builders (like dHive) to contribute. We should push to change that.
A quick update from our side: over the last couple of months, we’ve experienced significant spikes in unusual activity on our website, likely involving bad actors and possibly DDoS-like behavior. We addressed the issues by implementing stronger firewall rules and enhancing our CAPTCHA protections. We also reviewed integrations and resolved several related issues, including third-party rate-limit errors.
At the moment, we are operating in maintenance mode. To reduce ongoing costs, we’ve taken several measures that may result in reduced performance, and we are exploring sustainable ways to continue indexing new data as our current quota is nearly depleted.
In the coming year, we will evaluate our options to determine the best path forward. We want to be transparent with the community: development is currently on hold, but the project remains online in maintenance mode.
Thank you for your understanding. We’ll keep you updated as things evolve.