Proposal Overview
This is a proposal for:
- Adding SpookyG as the 8th multisig committee member and m.sig Committee Lead
- Revoke the Blox DAO multisig key within 3 months from execution of this proposal.
Motivation
Since the inception of the SSV DAO, Blox has held a multisig key as part of the multisig committee. This initial setup was made to ensure a rolling start for the SSV DAO.
The SSV DAO was always meant to be in complete community control, and time has come to take that next step. Blox proposes to hand over the Blox multisig key to the community through community ambassador SpookyG.
As a community ambassador SpookyG has helped grow the community and has always been active and available on the DAO forum and Discord. SpookyG has also held the “Master of Coin” role and helped the community get an overview of the DAO Treasury and proposals through the community treasury sheet. As part of this role SpookyG has also helped facilitate multisig committee operations.
Dune dashboard built by SpookyG: Dune
DAO excel sheet: SSV DAO treasury - Google Sheets
Undertakings
- When necessary, Spooky will initiate m.sig rounds following successful DAO votes.
- DAO votes which require multi sig execution will be submitted to the committees’ review once a month
- Spooky will aggregate successful DAO votes to m.sig execution rounds and avoid “spamming” the committee by requiring the committee members to separately sign on passed votes
- In case Spooky is no longer able to undertake the committee obligation he will try to the best of his abilities to propose a substitute committee member to assume the Committee Lead’ responsibilities.
Mechanics
0x872Da650d6d727b87e56D8e46f62228a27f94B3d Added as multisig signer, Safe policy changed to 5 of 8 Signatures
0x656DC25464941bD0A017E3babF49b61D437693BB Retired in no later than 3 months, Safe policy changed back to 4 of 7 Signatures