Comment on page
Guards [Multisigs]
Information about guards initiative, also known as multisig signers.
Multisig roles were split into a financial-treasury and technical. Both multisigs were created prior to the deployment ceremony by previous initial core members, as contracts needed to know the wallet addresses. Then, multisig members and a signer count requirement were added after DAO voting procedures. All this can be verified on-chain and Etherscan in logs of respective contracts.
Multisig must execute whatever proposal reaches winning quorum. Given that multisig are members previously enacted by token holders, meaning the DAO, and are semi-public people with big reputation - in extreme cases they could voice against implementing some proposal. However, that could breach trust in the governance model and require immediate action and restructuring. This must be exercised carefully.
List of members on the multisig:
- 1.
- 3.
- 4.
- 5.
- 6.
- 7.
- 9.
- 10.
Technical Multisig will not have a timelock function just yet, for security purposes. The pause function was awarded to 2 analytical addresses, while the unpause function is in the hands of the same technical multisig, but a 3/10 for better response time. That is 0xbb803559b4d58b75e12dd74641ab955e8b0df40e.
List of members on the multisig:
- 1.
- 2.
- 3.
- 6.
- 7.
- 8.
- 9.
Information on technical multisig transactions as well as votes (all representing changes to the technical architecture) will be often communicated on Discord here:
Join the Gearbox Protocol Discord Server!
Discord
voting and multisig report channel