Hi all,
Thank you very much for all the comments so far!
We are very excited by the response from the community to the new vision. Let’s take this time to answer some of the questions raised and continue the discussion. Given the quantity of responses, we’ve grouped individual questions into common themes to avoid repetition and keep the answers concise.
- Delegates are still primarily responsible for making decisions, including approving or denying a proposal, but will most proposals go through an AAE?
Yes, OpCo will be responsible for acting as the router to ensure proposals are reviewed by the appropriate AAE and feedback is given transparently on the forum. If the AAE agrees the proposal is worth pursuing, they will undertake the task of getting the proposal through the DAO process and hopefully receive delegate approval. The AAE will then be responsible for its execution, acquiring vendors as needed, and working towards a positive result for the DAO.
Most importantly, as some commenters alluded to, tokenholders and delegates are not rubber stampers. They retain control of the on-chain treasury and software, and are the ultimate decision-makers. As outlined in the vision, they can pass proposals even if an AAE disagrees with them, and it will be up to the OpCo to hold the authors accountable to what was promised to the DAO.
- Is there an example of a proposal that was previously approved by the DAO, and how it might be different with the new vision?
Let’s take a look at the Arbitrum DAO (Domain Allocator Offerings) Grant Program (Season 3) proposal.
The proposal currently focuses on five domains: gaming, education, dev tooling, new protocols and orbit chains. It highlights the program’s past success, including a list of initiatives that it has funded and considers successful (e.g., Devrel Uni). It also includes compensation for each domain allocator and the program manager (JoJo, Juandi, Seedgov, Flook, MaxLomu and CastleCap).
In the new vision, the proposal should continue to promote the merits of the DAO grant program alongside potential domains that can be funded. The main difference is that the proposal should focus more on holistic goals (i..e, what does success mean for the program?) and not the operational details. For example, the DAO grant program proposal should be formulated in a vendor-agnostic manner and it should be an AAE, like OpCo or AF, that endorses the proposal and not an external service provider like Questbook.
If the proposal is passed, the allocated AAE will procure an appropriate vendor, which may or may not be Questbook, along with a negotiated service level agreement. The success of a DAO grant program should not depend on the platform (such as Questbook), but rather on the merits of the idea. If Questbook were to disappear or fail to meet the service level agreement, then a new vendor could be selected without going through the DAO process, ensuring the program can continue to function without significant interruptions.
If contributors are involved in the proposal, we expect the AAE to conduct a screening process to vet candidates to ensure they possess the necessary skills for the role. After the screening process, it will either be up to the AAE to select which contributors take on the job or a DAO election can be used. We do expect DAO elections to be used more sparingly and focused on more critical initiatives (e.g., selecting the OpCo’s oversight committee).
All contributors who are engaged with the program should have appropriate agreements signed with the relevant AAE as the counterparty. The agreement should outline the scope of work, compensation details, and be used to help monitor their performance and ensure they meet the DAO’s expectations. If the contributor is executing the role to the expected standard, then fantastic, but if they are not living up to the DAO’s expectation, then the AAE is expected to terminate their role.
Additionally, we expect the AAE to be more heavily involved in the proposal’s execution. This may range from helping pick domains, providing advice on individual grant applications, and some of the operational heavy lifting. It is ultimately up to the AAE to bear the responsibility to ensure the program is successful and the operations undertaken by the AAE should reflect that.
Note, none of the above should be viewed as a criticism of Questbook or any of its current contributors. It is simply an illustration of how the proposal may change if it is proposed to the DAO in the new vision alongside how an AAE is involved in supporting its execution.
- Empowering new AAEs should not come at the expense of contributors in the DAO.
The intention is to leverage the resources available from the five AAEs to help execute on proposals. A contributor can bring ideas to the DAO, and if the AAE believes a proposal should be implemented, they can take charge to push it through the appropriate processes to ensure its implementation.
The main idea behind the vision is that an AAE, and not contributors, bears the responsibility to ensure a program is successful and the operations undertaken by an AAE are expected to reflect that reality.
An AAE will be responsible for screening applicants, and in many cases, picking the applicant who is most qualified to carry out the task. The hired contributor will be engaged as a consultant with the relevant AAE working within a well-defined scope of work. They will work closely with the AAE to ensure there is regular feedback to support them in carrying out their duties.
If successful, we expect to see more contributors and service providers get involved in DAO approved programs.
- AAEs feel centralised and the process of picking a new AAE is important. What should we think about this?
To date, the ArbitrumDAO has organically created the majority (three out of five) of the new AAEs, including OpCo, GCP, and Entropy Advisors. Additionally, the DAO has the authority to appoint or remove the AF’s directors and has control over the AF’s vesting budget. In each case, the delegates and existing AAEs (AF/OCL) acknowledged the need for a new dedicated team to tackle a specific vertical within the DAO.
In some cases, this means that an existing AAE can relinquish some of its work on a vertical (like blockchain gaming) to allow a new team to arise that can dedicate significantly more attention to it. In other cases, like Entropy Advisors, there was a missing hole to fill in the DAO that existing AAEs were not executing on, especially around shepherding key partners through the DAO process, visual data dashboards, and strategic proposals.
Creating a new AAE should not be easy, as it’s essentially bootstrapping an entire new dedicated team. As we have seen, new AAEs will spring up when everyone has reached the rough consensus that it is needed. Additionally, the formation of a new AAE should not be viewed as a limited-time initiative that expires, but it should be set up to ensure the AAE will be here for the long run across a multi-year horizon.
- How will the DAO hold the AAEs accountable?
At present, the ArbitrumDAO has control over the OpCo, GCP, and AF via on-chain governance, including replacing oversight committees and directors of the organisations. With future AAEs, we expect the OpCo to take on the role of holding AAEs accountable to their commitments towards the DAO.
There are several reasons why we think this is desirable.
First and foremost, the OpCo’s sole mandate is to represent and support the DAO. It has no other mission statement than making sure the DAO is successful. Second, the oversight committee (OAT) is elected by the DAO to represent their interests and will have access to information that cannot be publicly available, alongside being able to resolve issues without undue attention from the public. Finally, the organisation as a whole will have resources to properly vet and perform due diligence on deliverables.
Note, this does not mean an AAE should not communicate with the DAO. Just like the AF with its bi-annual transparency reports, all AAEs are encouraged to publish their results to the ArbitrumDAO, to keep the community informed on successes (and failures), and to bring the community on the journey with them. After all, the DAO should be the AAEs’ biggest cheerleader, and that is only possible if the AAE is transparent.
- There should be a second tier of entities and contributors who are still strongly aligned and for whom Arbitrum winning is also mission-critical to their success.
We did not intend for this post to imply that there are only five organisations that care about Arbitrum succeeding. Arbitrum is a significantly large ecosystem with many teams, builders, and contributors who want to see Arbitrum win. The ArbitrumDAO to date is a testament that this is indeed true, with its activity and ability to have an impact over the past two years.
All AAEs, certainly the AF, want to work more closely with teams that see their success dependent on Arbitrum and/or want to see Arbitrum succeed, which is what this vision is attempting to achieve. We are a little cautious about declaring a second tier of entities as it feels slightly undermining to the contributions of those organisations.
If you’re a team, project, or contributor that truly wants Arbitrum to succeed, then we’d anticipate that this vision will help them work more closely and hand-in-hand with the AAEs.
As well, the new vision should enable more Arbitrum-focused teams to participate as delegates to help share our ecosystem’s future. This is because the barrier to entry into the DAO should be a less taxing event. They can vote on strategic decisions and rely upon dedicated AAEs to execute on the operational details.
- Redundancy across AAEs in the support services like recruiting, finance, etc. How can we deal with this?
There are some functions that must be independent for each AAE (e.g., general counsel or finance for internal budgeting). However, when possible, it is feasible to share resources across different AAEs.
One example is recruiting. If an AAE interviews a candidate who does not fit the job description, but their profile is suitable for another AAE, then with the applicant’s permission, the profile should be shared. Current AAEs already do this for candidates who are interviewed. Another recent example is event planning, as the AF, OCL and GCP worked together to ensure Arbitrum had a significant presence at GDC.
The main consideration here should be that AAEs must be synchronised with each other and ensure they share resources to help each other succeed. We are lucky to already have a culture that enables this process, and we must ensure it is maintained as the ecosystem continues to grow.