The official discussion for the Treasury Covers Costs for Creation of Radicle Orgs proposal. With this post, the proposal has entered the second phase of the governance process. Please review the drafted proposal and contribute feedback by Sunday, November 7th.
We’d like the Treasury to fund a multi-sig for reimbursing gas fees incurred from creating Radicle Orgs. The goal of this initiative is to support the adoption of Radicle Orgs by reimbursing gas fees for the first 200 Orgs created on mainnet.
The reimbursement fund will be managed via a multi-sig governed by 3-5 individuals involved in Radicle project & community:
- @abbey* - Community Team Lead
- @nas* - Community Team Contributor (Partnerships Lead)
- @larry* - Radicle Governance Working Group Contributor
Potential additional candidates:
Users that create new orgs can submit a reimbursement request to the multi-sig to cover the transaction fees of their org creation.
The initiative would cost $200,000 USDC and be funded via an allocation from the Radicle Treasury (See Reasoning and Analysis for a cost breakdown).
Radicle Orgs are one of Radicle’s most exciting new features built on Ethereum. Radicle Orgs — on-chain entities owned by multi-sigs (i.e. Gnosis Safe) — offer a transparent & universally verifiable way to manage and distribute ownership of codebases.
Today, creating and deploying an org on mainnet is very expensive (up to $1k) and constantly fluctuating due to gas costs. This cost presents a barrier to entry for new users looking to starting using orgs.
As we wait for orgs to land on L2, it’s important that we think critically about how we can make onboarding projects to orgs easier so we can increase usage & adoption of Radicle’s Ethereum features.
This proposal is a short-term solution for stewarding adoption of Radicle Orgs. We believe this will get more people using & experimenting with orgs, which will support the success of the feature in the long-term. Additionally, our current onboarding efforts are significantly hindered by the cost burden of org creation (see below).
If reimbursed users don’t end up using or maintaining their org after subsidized creation, product teams can use this as a community signal that the orgs value proposition needs to be improved/revisited.
Radicle Orgs needs better marketing or the product features need to be enhanced to improve the value proposition to users. Either way, I believe the protocol should be willing to pay for this information via the subsidy of Radicle Orgs.
While 1000 orgs was the original suggestion, @nas made the point that focusing on onboarding 100-200 well-established/larger projects could work better with our partnership strategy.
At the upper limit of that range, we’d expect a budget of ~$200,000k/50ETH. Incurred fees would be bundled per org, and the initiative would last until 200 orgs have been reimbursed or the funds depleted. From there, the community could evaluate the effectiveness of the program and decide on the parameters of its replenishment & continuation.
- A Gnosis Safe multi-sig managed by 3-5 individuals from the Radicle community (1 of 3/5 quorum) and funded by the Treasury ($200,000 USDC)
- An Airtable form & workspace for managing & tracking reimbursement requests
- [OPTIONAL] An official version-controlled repo documenting distributions for transparency. (maybe could be controlled by a Radicle Org managed by the members of the Growth Workstream?)
This proposal will make it easier and less expensive for new users to create orgs which we believe will help support long-term adoption of Radicle features.
Additionally, we believe that using the Treasury to fund growth & adoption initiatives is a very exciting opportunity. We’d like to use this proposal as case study for the type of Treasury-funded growth initiatives we see being created, proposed, and funded by the Growth Workstream.
- Who is responsible for managing reimbursement requests?
- Is 200 orgs a large enough sample size for testing the effectiveness of this initiative?
- Should we have this managed by a Growth Workstream org?
- What criteria do we want to introduce for reimbursement requests?