@joanbp, thanks for raising these questions.
No overall day-to-day impact to the DAO processes or powers.
Why this is needed now
-
For the SPR component: This proposal shifts the day-to-day operational TXs from the DAO multisig to spr.dao.superfluid.eth operated by the SPR program manager and the core engineering team. The DAO mutisig still approves onchain transactions for the campaign budgets as approved by the DAO. But the subsequent operational transactions, for example to start the individual campaign streams at a specific date and time (which need to be synchronised with the claim app website being ready with each individual campaign’s parameters and the marketing team announcement readiness) will be done by the core team engineers. As the number of signing requests from the DAO multisig has increased, without this we could end up with delays in program launches as it’s difficult to guarantee all DAO multisig members will be available when every campaign needs to be launched (which is at different times as determined by each campaign). ETAs from budget approval to launch campaigns under this arrangement will likely be around 1 day instead of current 3.
-
For the Treasury Committee component: This step clarifies the relationship rather than changing it so that operational wallets and roles are explicitly authorised by the DAO rather than implicitly assumed. This is particularly necessary now as we move towards the final steps of execution of SIP 9 in the coming weeks
Accountability and Transparency
- All of the relevant wallet addresses linking to their activity will be shared in the Forum here.
- Treasury Com would also be expected to issue DAO updates on their actions.
- As the Treasury Com would exist by DAO mandate, its authority can be modified or revoked by the DAO in accordance with the Constitution.
- Of course the door is always open to improve and update this arrangement, as we are learning from the process.