Summary:
Allocate 10% of new JBX reserved for dao.jbx.eth to Juicebox frontends each funding cycle.
Motivation:
The best way to guarantee Juicebox’s future is through decentralization.
juicebox.money is a major centralizing factor. Encouraging new frontends not only expands the Juicebox ecosystem—it mitigates major risks to contributors, the community, and Juicebox in general.
Risks:
-
There are risks inherent to decentralization. Juicebox does not have authority (or resources) to vet each new frontend to the Juicebox protocol. People might get scammed, websites might break, and rugs might be pulled.
-
JBX distribution is still tied to the multisig. Until a move to onchain governance, this system will inherit all the risks of Juicebox governance in general.
Specification:
Allocate 10% of new JBX reserved for dao.jbx.eth to Juicebox frontends each funding cycle.
To claim this JBX, any interested frontend must implement a tag. The tag should be prepended to any memo text entered by a contributor, with the format &X&text, where text is the contributor input and x is a hexadecimal representation of a Juicebox project ID. Frontends should also filter out this tag when displaying contribution memos.
Each funding cycle, distribute this JBX allocation to Juicebox projects listed in these tags, in direct proportion with the associated volume (measured in ETH).
Rationale:
-
This tagging system is compact, and using the memo field will allow for very quick deployment. This system also means that these frontends must themselves be Juicebox projects.
-
Reserved JBX is tied to total protocol volume, aligning incentives—this will encourage the growth of the Juicebox ecosystem.
Timeframe:
The JBX reserve for frontends should be re-evaluated in FC#20, and be increased if there is more frontend competition.
Copyright Disclaimer:
Copyright and related rights waived via CC0.