Synopsis
Fund the nance Juicebox project $11,000 per funding cycle for 7 cycles (total $77,000)
Motivation
Over the past few months twodam, jigglyjams, and nicholas have been collaborating and built the following features:
- Proposal content search - this is major improvement and was not possible using notion (only titles could be searched)
- Proposal editing on jbdao.org - editing proposals on jbdao.org ensures that the original author is the only one that can edit (as they must sign a message on submission)
- IPFS image hosting for proposal uploads - when you paste an image here in the proposal editor, it is pinned to ipfs (using https://nft.storage), this is another major improvement over notion as the images will show up properly when the proposal is pushed to snapshot
- Auto push to dolt - dolt provides git like functionality for mySQL databases, this allows us to roll back the database if there are ever any technical issues, a github action is used to query for new proposals and push to dolthub in the event there is a new proposal (https://www.dolthub.com/repositories/jigglyjams/juicebox)
- Better proposal stats - (mostly done by twodam) the beautiful main proposal page now features stats on how many unique addresses have voted on a proposal
- API endpoint to create a nance instance - this endpoint creates a new database and nance config file for an organization, still need to develop the frontend to properly interact with it
- Tenderly simulation submission - this sends all reconfigureFundingCyclesOf transactions to a Tenderly fork and advances time by 6 days to ensure that configurations can be properly distributed, this helps mitigate silly reconfiguration bugs (developed in collaboration with Dr.Gorilla.eth, thanks fren)
- Reconfiguration helper - this has become an essential part of the multisig reconfiguration process by showing the different project updates in a user friendly way, this replies on the nance-api to retrieve the recurring payouts submitting through proposals (https://www.jbdao.org/juicebox)
- Discord transaction threads - this feature saves us a lot of time by automatically showing in Discord any new payouts or payouts that have been removed from the next funding cycle
- Discord bookkeeping - this shows all payouts for an upcoming governance cycle along with how many payouts have been sent for a given proposal
There are some new features that we have in the pipeline that we are excited to build:
- Attaching "actions" to a proposal - this will allow a proposal author to add actions to perform on the passing of a proposal (see mockup below), this will help ease efforts from the multisig whom normally has to hunt down the author to find out exactly what they wanted to perform after the fact
- Further improve proposal metrics - add average voter turnout and voter turnout per funding cycle (simple mockup below), this will allow the DAO to understand how many voting members are coming out for each governance cycle and begin ot understand what causes more DAO engagment
- Create nance instance UI - in order to spread nance to more DAOs, we need a simple UI to create a nance instance, the API endpoint ot setup the database is there, we need to tie it together with a tight UI that makes it easy for anyone to test out using nance
- Explore different funding options - finding a governance business model is hard when there are so many good free things out there, nicholas has some awesome ideas on how to keep nance an open source, publically funded good; gitcoin, optimism, or other large DAOs have the potential to keep us paying our devs
- Integrate accounting - there is a lot to explore in the bookkeeping and accounting world still, we are very interested in integrating accounting tools with nance so DAOs can have a one click export of all of their JB and multisig transactions
- Public Read/Write for dolt - this will move nance to a true decentralized database
- Documentation and about page - this is necessary in order to explain nance to outsiders and apply for new grants (this will also help with explaining how to self host a nance instance)
- Improve forkability - refactor nance-auto, nance-api, and jbdao.org frontend to be easily forkable for other organizations, extract hooks (snapshot, juicebox)
- Improve mobile site - make jbdao.org more mobile friendly
Specification
The nance juicebox project will be own by a 2/3 multisig with jigglyjams, twodam, and nicholas as the signers.
Expenses to operate nance are quite low (~$100/month):
The main use of the funds will be to pay our contributors:
- jigglyjams - $4,000/cycle (used to cover time and expense)
- twodam - $5,000/cycle
- nicholas - $1,500/cycle
===================
$10,500 (total contributors payout)
+ 500 (overflow to be kept in the project)
===================
TOTAL request $11,000/cycle
twodam's recurring payout from JBP-323 shall be cancelled once the $5,000 is properly configured to be received from the nance juicebox project
All remaining funds will stay in the nance juicebox project to be used at a later date to pay devs.
By the end of these cycles all proposals shall be submitted through jbdao.org or some custom frontend, notion shall no longer be used. This will ensure that nance works well enough to provide the service that it set out to build.
Note: the nance juicebox project will be setup before the end of voting and the payout shall be directed to that project once it is setup
Risks
The nance team may fail to do this job properly
Mitigations:
- jigglyjams has been heavily involved over the past 9 months and very much enjoys this work and being apart of JB
- the nance team of nicholas, twodam, and jigglyjams have been meeting regularly to further speed up the development process of the platform
Timeline
This proposal shall take affect in GC#45