You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the continuation of the SaberDAO revival story, the efforts have to be expanded and the DAO needs the capability to see things through and have active contributors pushing the protocol forward. Therefore, a new organizational setup where I (c2yptic) is not leading SaberDAO anymore, but the DAO and protocol operations will be led by a cohort of people and these people need to get compensated to be able to work in a meaningful way.
Motivation
New organisation suggestion
SaberDAO can not have just one guy who pulls the strings, moving forward we want to enable the contributors to take full charge of SaberDAOs future.
The dApp needs long-term developer support, but for the Saber Wars to really reignite, we need to see to the communications and business development side of things.
With the involved contributors, I suggest structuring the Organisation for the next 12 months as stated below. Please note that I can personally vouch for all of the people mentioned:
3 DAO Working Groups
Operations: manage wip projects, manage new projects, products, dev, finances, BD)
The Operations will be led by: Rockoor, JS and J.Lee, supported c2yptic(me) who is now taking a more advisory and guiding role.
Community Council: Veto power on proposals based on a council vote (through a socially enforced mechanism in the short term), before or after. Guardians of the DAO.
This makes sure that the DAO has a group of active contributors willing and motivated to actively push the protocol forward in all necessary directions, and with a community council we ensure that the ethos of the DAO stays intact.
For these 3 working groups to work efficiently, with a fair long-term alignment, we need to compensate in both USDC and SBR. (This proposal is about operational expenses, ie. USDC. The SBR long term alignment will be handled in a separate proposal)
Total working group 12-month budget USDC: 320,000 - To be managed by the DAO Ops Leads.
Actions
Issue 320,000 USDC to SaberDAO Ops Mutisig wallet: C8vvHyFKiuAqdugpVtrALV8iS1smPsb4NzPrpNjP5Qpn
The text was updated successfully, but these errors were encountered:
Summary
For the continuation of the SaberDAO revival story, the efforts have to be expanded and the DAO needs the capability to see things through and have active contributors pushing the protocol forward. Therefore, a new organizational setup where I (c2yptic) is not leading SaberDAO anymore, but the DAO and protocol operations will be led by a cohort of people and these people need to get compensated to be able to work in a meaningful way.
Motivation
New organisation suggestion
SaberDAO can not have just one guy who pulls the strings, moving forward we want to enable the contributors to take full charge of SaberDAOs future.
The dApp needs long-term developer support, but for the Saber Wars to really reignite, we need to see to the communications and business development side of things.
With the involved contributors, I suggest structuring the Organisation for the next 12 months as stated below. Please note that I can personally vouch for all of the people mentioned:
3 DAO Working Groups
The Operations will be led by: Rockoor, JS and J.Lee, supported c2yptic(me) who is now taking a more advisory and guiding role.
This makes sure that the DAO has a group of active contributors willing and motivated to actively push the protocol forward in all necessary directions, and with a community council we ensure that the ethos of the DAO stays intact.
For these 3 working groups to work efficiently, with a fair long-term alignment, we need to compensate in both USDC and SBR. (This proposal is about operational expenses, ie. USDC. The SBR long term alignment will be handled in a separate proposal)
Actions
Issue 320,000 USDC to SaberDAO Ops Mutisig wallet: C8vvHyFKiuAqdugpVtrALV8iS1smPsb4NzPrpNjP5Qpn
The text was updated successfully, but these errors were encountered: