Welcome to August 2023 Cycle Proposal Review! These calls are a time for proposal authors to present their proposals and answer questions from the community before they move through the voting process in the current cycle. The proposal in the Discussion phase listed below will move on to the Formal Review phase of governance, including a Snapshot poll, next week (August 14th).
Active Discussion for this cycle:
[Discussion] Fund Radworks Dependancies with Drips: https://community.radworks.org/t/discussion-fund-radworks-dependencies-with-drips-proposal/3357/13
02:16 Proposal overview from proposal author
12:16 Transaction Flow & Proposal Code
19:14 Which Orgs & splitting of funds
33:15 Duplicates of dependancies between Org lists
34:01 Changes to dependency lists
45:42 What happens after fund start being streamed? How are recipients supported?
SUMMARY of Discussion Points & Questions from the call:
- Proposal Code - what will the contract calls be? Are there risks to be aware of?
- Code will transfer 1M out of treasury & deposit into Drips protocol contract, create a dependancies list (made up of org lists), and start streaming into each Org lists
- Fairly low risk, but still want to outline more clearly what the review process for the proposal code will be and model & run on testnet to prep (ok if this happens during Formal Review)
- Org Dependency lists
- Drips already has a list together and has been in contact with other Org leads about theirs
- There was a discussion around if these lists should be able to be changed over time or not. There seemed to be consensus that Orgs should be able to change the lists, but there should be a clear process around how and why, as well as how it will be communicated with the community for transparency
- Splitting of funds: (pasting from previous comment)
- In regards to splitting of the $1M RAD/USDC, how do folks feel the funds should be split between each Org? Some examples discussed on the call:
- All equal % split
- % based on proportion of funds allocated to each Org in the annual Org proposals
- Higher % for product Orgs who have clear software dependancies vs Foundation or Grants
- Should the Foundation Org be included? Or should the funds for dependancies be distributed amongst Orgs who have clear dependencies in this version of the proposal (i.e. Radicle, Drips, Grants)
- Consensus of folks on call was that the fund split should be more focused on Orgs with clear software dependancies (which at the moment are the two product Orgs (Radicle & Drips) and Grants, but not so much the Foundation Org)
- Could also consider reducing the $1M if less Orgs are included? Argument being wanting to keep more USDC in the treasury.
- What happens after the funds have been streamed / does the support process for recipients of the funds being streamed look like?
- The Drips team already has been in contact for folks on their list and has an outreach plan to get in contact with recipients from other Orgs’ lists once there has been a decent amount streamed. They will help recipients onboard and claim their funds.
- Is there anything needed from the community at this time?
- Andrew: It would be great if Orgs could share more about their process on how they decided on dependancies for their Drips lists.
- Recommended additions/clarifications to the next draft of the proposal that were discussed:
- Add proposal code & review process for code
- As there seemed to be consensus on the forum that duplicates of dependancies for different Orgs are ok - clearly state that & provide reasoning around why
- Clarify that dependancies on Org lists should be external recipients to avoid conflict of interest
- Clarify that a list can change & explain process for how/why and how communicated with community
- Include % of split across Orgs and average stream per dependency
- Include dependency lists from each Org that will be included (ask Org leads to give brief explanation of process for choosing dependancies)
- Explain what happens after Drips start - how dependancies will be notified and supported to claim drips, etc.