Just to clarify the reason items are “not included” (yet) is due primarily to the limitation of the funding that the ESD can release. Our S2 funding strategy states:-
Thats said dGov could cover the 5k funding required for the community engagement process which would cover the
- 4k advance payment to General Magic for the development of the Commons Config dash and
- TEC community engagement aspects - proposed parameter parties, param debates and the AMA sessions.
Clearly 10k will not cover the cost of things such as audits and @sembrestels and @paul2 would need to advise on the costs to
- Include disputability, enabling the DAO to be secured by a Charter and dispute service
- Customise the DAO frontend
- Create a custom frontend to 1) apply as a delegate and 2) delegate voting power
As 40k is effectively the limit of ESD funding would that be enough to achieve 1-3 ? Although if this extends the time line beyond two (2) months, we could allocate up to 60k or 80k MAX (due to timeline, if just tweaking the delegate UI UX in November)
//
A Main DAO proposal could be created, it simply delays development by a further three weeks. Given the October deadline for delegates, I am 1/3 in support of providing what funding we can via ESD so development for the demo can progress, while additional funding is secured via Main DAO for the work that proceeds the Demo
Ultimately a Governance proposal is required to decide on the alternative governance tooling. For governance legitimacy this requires
- a tech agnostic charter CIP 1 and
- a minimum of 30 Days of Notification + 14 days of voting + 0.5% quorum CIP 2
Voting scheduled to being 22 July
Given timelines to have delegates in place ahead of S3 - 1 December to 31 March - we would need governance proposals for the delegate DAO on the forum by end of August. The strategy here is to provide a working demo to help inform voters as to the options on the table.
