Proposal for a new Nest application process including the Nest DAO
Note: an Association Track AGP will be created out of this document and the feedback provided. This first change is part of a bigger NestV2 plan which aims at gradually refreshing the current Nest program.
Until now AA has had the responsibility to decide on Nest grants allocation. On the path to a fully sovereign and autonomous network, the Aragon Association will increasingly delegate strategic decisions to the Aragon community. In Nest V2, Flock teams will take part in grant allocation decisions through appointing a group of team members to the Nest DAO. A new process is designed for this purpose where the Nest DAO has the final say over grant allocation and the Aragon Association steps back in a more coordination and advice oriented role.
The Nest DAO
Each time they get voted-in by ANT holders, Flock teams submit an application for some of their members to join the Nest DAO.
- Members of the Nest DAO have a non-transferable membership token enabling them to vote
- The Nest DAO votes on grant allocation decisions
- AA is in charge of funding the Nest DAO as per AGP proposal for the Nest budget
- Nest funds are held in the Nest DAO
- Grantees are paid through the Nest DAO
- The Nest DAO members also form an Aragon Working Group
- Should the Nest DAO approve the Nest budget proposal submitted to ANVs?
Membership for the Nest DAO
- Be the member of a Flock team
- If members of Nest DAO do not vote, they will have to justify it to AA, otherwise teams can loose their membership tokens for the period
Application for membership
- Each Flock team can appoint a group of team members to the Nest DAO
- In order to do that, Flock teams need to submit a short application explaining why they think the group appointed makes sense (is complementary) and will add expertise and judgement to the Nest DAO
- For the first membership round, AA will be in charge of accepting/rejecting applications
- Once application has been accepted by AA, team members will have to submit identity verification using Keybase to receive their token
- Should there be a max number of participants from a given Flock team?
Governance settings and permissions
- 1-person, 1-vote
- Super majority support: 67%
- High quorum: 67%
- Vote durations: 10 days
- AA mints/burns and allocates tokens at first, then this job is handed out to voting app
- Question votes can be created by anyone
- AA will remain in charge of triggering payment votes
- As votes can be created by anyone, the Nest DAO is subject to spam attacks. If the Nest DAO is under a spam attack it will have to coordinate to change the permissions. A more centralized alternative is to leave the ‘create vote’ permission to AA for now
Application for a Nest grant - what’s new?
In Nest V1
- Create an issue with proposal idea asking for feedback
- AA provides feedback whether if idea is worth pursuing
-Provided that proposal idea is approved by AA-
- Team can submit a request for funding
- AA provides feedback and approves most of the time, sometimes not
Who is involved in grant allocation?
- Nest Manager and Executive Director at AA are selecting grants
- They gather feedback and opinions from Flock team members directly impacted by the proposal
In Nest V2
- issue with proposal idea asking for feedback for a minimum of 30 days unless it has authorization from AA to move on
- AA coordiantes with Flock teams to provide feedback if necessary
- AA encourages/discourages to submit a request for funding
-Provided that proposal idea is encouraged by AA-
- Applicant team submits a request for funding
-If proposal idea is discouraged by AA-
- Team can still choose to request for funding and go for a vote in the Nest DAO
-In any case, if request for funding is approved by Nest DAO-
- Applicant team has to submit a verified Ethereum address, for example using Keybase’s signature system
- A payment vote to the provided address is triggered by AA
Summing up: who is involved in grant allocation?
- In Nest V2, AA doesn’t have the ability to strictly reject proposals
- In Nest V2, AA has the role to provide the right feedback to challenge and shape up proposals, and coordinate to gather opinions if necessary
- AA emits a encourages/discourages Nest proposals providing a rational behind it
- AA emits an advice with a note to the Nest DAO
- In Nest V2, the Nest program goes one step further to a more decentralized making on the strategic decisions that are Nest grants by harnessing collective decision making to vote on applicants
Clarification of new concepts
- Application time: Proposals have to be submitted a minimum of 30 days before requesting for funding
- Forcing request for funding: Provided it has respected the application time of 30 days a team can decide not to listen to AA and force request for funding to access the Nest DAO voting round
- AA’s recommandations to applicants: AA can encourage or discourage applicants to submit a request for funding, emiting recommandations: higly discourage, discourage, encourage, highly encourage
- AA’s voting advice: AA has the ability to disclose a public advice on a given request for funding to the address Nest DAO voters. It is accompanied by a voting advice: Yes/No.
Zooming on AA’s voting advice notes
Voting advices consist in a short note disclosed publicly to the address of Nest DAO members. The content is a short summary and analysis of the proposal written by AA with a vote recommendation.
No longer than 500 words:
- Summary of the proposal according to AA
- How it seats in the Aragon Landscape
- Subjective opinion supported by clear rationale
Open to getting feedback on the specs given above.
Bonus: a new guide on the ‘Nest rational for grant allocation’ detailing a method to assess an application will come out soon.