Summary:

• Create a Frontend DAO (”Peel DAO”) comprising of the JB’s frontend contributors to internally handle frontend matters of Juicebox. Peel DAO would be created as a Juicebox project.
• Add Peel DAO to a recurring payout of US$30,000 (paid in ETH) per funding cycle.
• Remove recurring payouts for frontend contributors @peri @aeolian and @johnnyD
• Send 3.98566618 ETH to frontend multisig (address TBD). This is the ETH remaining from the previous allocation to JB multisig for infrastructure spending.https://snapshot.org/#/jbdao.eth/proposal/0xc1fba48670c743dcd4773b5def0b0e9d4102430aad1f19af0c16cbce4e23b51c, after single purchase of USDC to pay Infura billing https://etherscan.io/address/0x68b3465833fb72A70ecDF485E0e4C7bD8665Fc45.
• Send US$2,035.00 in ETH for 13-month Crowdin bill already paid by @johnnyD.

Abstract:

The frontend contributors are proposing to break into their own DAO (Peel DAO) to internally handle frontend matters of Juicebox and Juicebox projects.

Motivation:

1. Less complexity for Juicebox DAO. The responsibility to be familiar with individual contributions would be moved from Juicebox DAO to Peel DAO, removing some burden from Juicebox DAO voters. Juicebox DAO would only be responsible for considering proposals from the Peel DAO as a whole, rather than from individual contributors.
2. More agility for the frontend team. Without requiring new or existing members to go through the Juicebox DAO governance process, the frontend team would be able to onboard new members or adapt to changes in member roles more quickly. This would be especially useful for incentivizing folks to help out who may only be interested in short-term contributions, and for whom a 2-3 week proposal timeline may be a friction point.
3. Easier to provide services to Juicebox projects. This proposal will enable JB projects to approach the Peel DAO directly for frontend work, such as customizing their project’s juicebox.money page or JB integrations outside of juicebox.money, rather than the current much higher friction option of going through Juicebox DAO.

Risks:

The control of JB’s frontend matters, such as hiring frontend contributors, would be moved from the JB DAO to the Peel DAO. Over the short term, frontend decisions could be made by Peel DAO that the JB DAO disagrees with. However, it should be noted that if the Peel DAO consistently proves to be misaligned with Juicebox DAO, Juicebox DAO could easily propose to reduce or remove Peel DAO’s funding.

Specifications:

The Peel DAO will be owned by a multisig wallet comprising of the current frontend contributors: @peri @aeolian @Torvus Bug @Zhou Jason and @johnnyD. The governance process will be managed through this multisig, on a simple majority-vote basis (proposals will require 3/5 signatures to pass).

Responsibilities:

The Peel DAO would take on the combined responsibilities of all the frontend contributors, including:

• Maintaining any and all frontend-related work on juicebox.money, rinkeby.juicebox.money, and all related Juicebox interfaces.
• Design & implement a frontend experience based on changes to the JB protocol (such as V2).