We appreciate @Entropy commitment to the Arbitrum DAO and acknowledge the breadth of work delivered over the past year. The team has clearly become an integral part of DAO operations and has brought professionalism, energy, and valuable structure to many complex initiatives. As we consider a significant two-year renewal with an increased budget and a long-term ARB token alignment, we would like to raise several areas where the proposal could be strengthened.
As we review this proposal for a multi-year engagement with an expanded scope, we believe there are a few areas where additional clarity would help the DAO make a more informed decision. One of our main areas of feedback relates to the balance between execution and outcomes. While Entropy has helped ship many proposals and workstreams, we would appreciate a better understanding of the tangible results these efforts have produced. For example, the staking working group and STEP were thoughtfully designed, but how have they performed so far? What impact have they had on ecosystem growth, retention, or capital efficiency? What lessons have been learned? Sharing reflections like these would strengthen the proposal and build further trust in Entropy’s approach.
Looking ahead, we also note that DRIP represents a new direction for how the DAO approaches incentive design. While the program has not launched yet, it would be helpful to understand what indicators or metrics Entropy intends to track once it goes live, and what a successful outcome might look like. Planning ahead for evaluation can help ensure that we not only launch good programs but also learn and iterate based on results.
In that spirit, we would appreciate the inclusion of more clearly defined KPIs and reporting structures across Entropy’s scope. These tools would help the DAO assess performance more objectively and provide context around which initiatives have delivered the most value. Even a high-level roadmap or set of milestones for the next two years would help the community understand what success looks like. In addition, it would be valuable to know where Entropy believes its work has saved the DAO time, avoided inefficiencies, or unlocked growth. These kinds of outcomes are worth highlighting and, where possible, quantifying.
Regarding the proposed two-year term, we recognize the point made @JoJo , that longer terms can allow teams to focus more fully on their mission. At the same time, we would appreciate more context on why two years is specifically necessary in this case. Are there particular initiatives that require a full two-year cycle to complete? Is there a long-term strategy that maps to this timeline? Including examples or a roadmap that shows how the work unfolds over time would help make this decision easier for the community.
Additionally, we’d appreciate a clearer explanation of how Entropy’s mission aligns with the broader objectives of the ArbitrumDAO, particularly in relation to the SOS framework proposed by delegates. Could you elaborate on how your proposed workstreams support the key pillars of this framework? Drawing a more direct connection between Entropy’s role and the DAO’s strategic priorities would help contextualize the proposal within the larger ecosystem goals.
We would also like to see more detail on the proposed budget. A simple breakdown of how the three million dollars per year will be allocated, such as staffing, infrastructure, and other operational costs, would provide useful clarity. Similarly, the fifteen million ARB vesting package is substantial. We believe it would help to explain how this will be distributed within the team, whether there are clawback protections, and how the vesting contract will be managed. This ensures that incentives are well aligned with long-term performance.
We also welcome a brief discussion on the topic of exclusivity. We understand the benefits of having a high-context team dedicated to critical DAO functions, and Entropy has clearly served that role well. At the same time, we believe it remains healthy for the DAO to encourage complementary contributors across workstreams such as data, treasury, and incentive design. This supports a resilient contributor ecosystem as Arbitrum continues to evolve.
It would also be helpful to understand how Entropy plans to navigate its role as both a delegate and a service provider. We recognize the value of having context as a delegate and the positive impact that involvement can have, but outlining how potential conflicts are managed would help address recurring questions from the community.
Finally, if this proposal does not move forward, it would be useful to know what happens to the ongoing work. Are there plans to wind things down, transition responsibilities, or maintain certain operations? Clarity here would support better planning and help set expectations across the DAO.
Overall, we want to thank the Entropy team for all of the contributions made so far and for submitting this thoughtful proposal. With a few additional details, especially around outcomes, roadmap, DAO alignment, and transparency, we believe this can serve as a strong foundation for the next phase of your engagement. We look forward to further discussion and continued collaboration.