Formalizing the Community Multisig
01Summary
Proposal to formalize the Compound Community Multisig by adopting professional operational documentation and processes developed with DefiSafety, and establishing a 6-month trial budget of $84k ($72k for 8 multisig signers at $1.5k/month each, $12k for DefiSafety as quality engineer) to be funded via COMP token transfer.
- Type
- governance change
- Funding
- $84000
Key changes
- Adoption of formalized operational documentation, proof of humanity verification, and management processes for the community multisig developed by DefiSafety(high)
- Establishment of recurring monthly stipends for 8 community multisig signers at $1.5k/month ($12k total/month)(high)
- Creation of quality engineer budget for DefiSafety to maintain documentation, facilitate security checkups, and manage multisig operations at $2k/month(high)
- Renewal of community multisig powers including protocol emergency pause, proposal whitelisting, borrow caps, and malicious proposal cancellation(high)
- Implementation of regular multisig testing procedures to verify signer responsiveness and transaction execution across all chains(medium)
Notable concerns
- 6-month trial period implies potential future governance votes required for continuation
- Regular maintenance and signer changes will require ongoing revisions to documentation
- Proposal does not specify detailed criteria for multisig signer replacement or removal procedures
Generated by Kvorum
02Description
Formalizing the Community Multisig
Authors
@cylon, @PGov (CGWG), RexShinka (Defi Safety)
Summary
This proposal details an improved community multisig process and documentation. Working with DefiSafety, we have created a robust and detailed process to professionalise the community multisig to meet industry level security and opsec standards. This process improves transparency and clarity for the Multisig and ensures all signers are active.
Background
At Compound, the community multisig was initially created to:
- Pause the Compound protocol in case of emergency
- Whitelist accounts for submitting governance proposals that did not require a COMP threshold to be met
- Set borrow caps (Compound V2 only)
The power of the community multisig was recently modified to also include cancelling malicious proposals as well following the passage of Proposal 303 to add a Proposal Guardian. This power must be periodically renewed by governance.
Over the years, the process for onboarding and operational procedures for this very important multisig have been undefined. Over the last few weeks, the multisig signers have all internally doxxed themselves and worked together to set some ground rules for the responsibility. Using this momentum, we think it’s time to finally officialize the role and set expectations for the role.
The current multisig signers and members can be found here: Forums
Improvements
Through a Compound security tooling grant, DeFiSafety has developed base documentation, proof of humanity, and a history document for the multisig.
This detailed multisig document puts clearly in one place all of the documentation about the Multisig and its management process. This includes what the Multisig is capable of, who the signers are, what their responsibilities are, and their proof of humanity. It includes how the signers will communicate when an issue has been raised. It describes the regular testing and how the resulting executed transactions are documented. There is also a summary document which makes for quick reading. This document is a one-stop reference for the signers and the community on all aspects of the multisig. The grant funded an initial version of these documents. Revisions will be required.
DeFiSafety has a Proof of Humanity process that we used internally on the present signers of the Multisig. The proof of humanity document on chain is here, the description document is here. This will be revised if signers change in the future.
Performing regular tests will prove that all signers are able to sign rapidly and ensure that the signatures work on all chains.
Additionally, DeFiSafety developed an initial history document for the multisig. It includes the transactions from 2024 to the present. Which will be updated as new transactions and regular multisig testing take place.
Proposal
As indicated above, the initial docs and proof of humanity were funded by the grant to DefiSafety. With this groundwork, we propose finally officializing this community multisig. This includes (about 2 days per month):
- Formally voting to accept the rules of operation and processes for the community multisig.
- Establishing a recurring stipend for the multisig signers, similar to that of a security council.
- Creating a budget for DefiSafety to continue as a quality engineer. As quality engineer, DefiSafety will be tasked with keeping everything up to date with each transaction and any changes in signers, facilitating security checkups, and covering management tasks.
Budget
For an initial 6 month trial period, we propose
- Multisig Signers (8): $1.5k/month/signer => $72k
- Quality Engineer (DefiSafety): $2k/month => $12k
Total: $84k
The Compound Governance Working Group will be tasked with sending monthly remuneration payments and financial operations around such. There will be no extra budget needed for this.
The current price of $COMP when drafting this proposal is $39.22 which results in 2141.76 $COMP.
Lastly, this Multisig improvement makes the operation of the Compound protocol easier to understand for non-DeFi natives. Excellent clarity will make it easier for future investors to enter and working with DefiSafety, we will continue to identify other areas where better clarity and processes can occur.
Timeline: We will look to take this to a on chain vote in the coming weeks pending discussion and feedback.
03Mismatch analysis
A calldata-vs-description analysis is not generated yet. Review the decoded actions →
04Actions
- Target
- 0xc00e…6888
- Value
- 0 wei
- Function
- transfer(address,uint256)
- Arguments
{ "amount": "2141760000000000000000", "address": "0xfd947c72f09703210eeCbcab9c9206fE5e1Bb6e2" }- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 660x66cd…65f9 | For | 80.1K | 11.27% | — | 2y ago |
| B90xb933…8dd1 | For | 80K | 11.26% | — | 2y ago |
| 2B0x2b38…bf33 | Abstain | 80K | 11.25% | — | 2y ago |
| 070x0703…961b | For | 80K | 11.25% | — | 2y ago |
| 130x13bd…8548 | For | 80K | 11.25% | — | 2y ago |
| 3F0x3fb1…4c8a | For | 80K | 11.25% | — | 2y ago |
| B40xb49f…7948 | For | 80K | 11.25% | — | 2y ago |
| ED0xed11…bb04 | For | 50K | 7.03% | — | 2y ago |
| 050x0579…ca09 | For | 50K | 7.03% | — | 2y ago |
| B30xb356…c826 | For | 50K | 7.03% | — | 2y ago |
| CE0xce8a…8ca3 | For | 700.5 | 0.10% | — | 2y ago |
| 050x0579…4048 | For | 11.2 | 0.00% | — | 2y ago |
| 4A0x4a46…c1a6 | Abstain | 3 | 0.00% | — | 2y ago |
| 210x21b3…fa75 | For | 2 | 0.00% | — | 2y ago |
| B70xb792…89d7 | For | 2 | 0.00% | — | 2y ago |
| 8B0x8bb9…ccc2 | For | 1.1 | 0.00% | — | 2y ago |
| 170x1729…b879 | For | 1 | 0.00% | — | 2y ago |
| 2F0x2f2f…f78a | For | 0.5 | 0.00% | — | 2y ago |
| C60xc6d7…bfb2 | For | 0.1 | 0.00% | — | 2y ago |
| 610x61ff…9630 | For | 0.1 | 0.00% | — | 2y ago |
| 9A0x9a0f…8de8 | For | 0.1 | 0.00% | — | 2y ago |
| 190x19b4…9694 | For | 0.1 | 0.00% | — | 2y ago |
| 060x06c4…66a2 | For | 0.1 | 0.00% | — | 2y ago |
| 660x66dd…1e55 | For | 0.1 | 0.00% | — | 2y ago |
| AF0xaf0d…7c9e | For | 0.1 | 0.00% | — | 2y ago |
| 630x63db…8d03 | Against | 0.1 | 0.00% | — | 2y ago |
| B20xb2a6…72c3 | Abstain | 0.1 | 0.00% | — | 2y ago |
| 940x9451…ca19 | Against | 0.1 | 0.00% | — | 2y ago |
| 780x783d…45a2 | Abstain | 0.1 | 0.00% | — | 2y ago |
| 3D0x3dfe…4deb | Against | 0.1 | 0.00% | — | 2y ago |
| D80xd8de…ae41 | For | 0.1 | 0.00% | — | 2y ago |
| 0C0x0c66…ceca | Abstain | 0.1 | 0.00% | — | 2y ago |
| A30xa3b4…e192 | Against | 0.1 | 0.00% | — | 2y ago |
| 360x368f…6510 | Against | 0 | 0.00% | — | 2y ago |
| AB0xabd3…9856 | Against | 0 | 0.00% | — | 2y ago |
| 2D0x2de6…873b | For | 0 | 0.00% | — | 2y ago |
| 840x8469…ecd9 | For | 0 | 0.00% | — | 2y ago |
| 380x38dc…472d | For | 0 | 0.00% | — | 2y ago |
| 7A0x7a04…17a8 | For | 0 | 0.00% | — | 2y ago |
| A00xa0d0…604a | For | 0 | 0.00% | — | 2y ago |
| BE0xbef8…9999 | For | 0 | 0.00% | — | 2y ago |
| 210x21ff…c5a8 | For | 0 | 0.00% | — | 2y ago |
| D20xd248…32ae | For | 0 | 0.00% | — | 2y ago |
| 140x1475…6e15 | For | 0 | 0.00% | — | 2y ago |
| 950x95d2…88f9 | For | 0 | 0.00% | — | 2y ago |
| 930x93e0…f6ee | For | 0 | 0.00% | — | 2y ago |
| A70xa772…6171 | For | 0 | 0.00% | — | 2y ago |
| B30xb331…7174 | For | 0 | 0.00% | — | 2y ago |
| 470x47c0…4659 | For | 0 | 0.00% | — | 2y ago |
| B90xb986…2175 | For | 0 | 0.00% | — | 2y ago |
07Forum
- Community Multisig Deployment ↗discourse · high confidence
- [RFC] Formalizing the Community Multisig ↗discourse · medium confidence
Arguments for
None surfaced.
Arguments against
None surfaced.
Notable participants
- arr00Core steward of the Community Multisig, initiated its deployment and managed signer changes throughout.
- calvinProvided initial documentation and updates on the multisig deployment and signer confirmations.
- gettyConfirmed multisig members' comfort with additional responsibilities before governance vote.
- adamDocumented and tracked multisig membership changes and signer updates.
- PGovParticipated in recent multisig membership reevaluation and provided detailed status updates.
- jbass-ozAnnounced addition of ChainSecurity and Certora as signers and threshold increment.
- blckOriginal multisig signer who confirmed acceptance of responsibilities.
- TennisBowlingCommunity member who replaced aaaaaaaaaaaaa and later was removed during membership reevaluation.
Generated by Kvorum
08Similar proposals
- compoundexecutedRenewing the Community Multisig91%
- compoundcanceledRenewing the Community Multisig90%
- compounddefeatedRenewing the Community Multisig89%
- compoundcanceledTrust Setup for DAO investment into GoldCOMP68%
- compounddefeatedTrust Setup for DAO investment into GoldCOMP68%
- compounddefeatedExtension of the COMP Yield Strategy67%
- compoundexecutedResubmission: Extension of the COMP Yield Strategy67%
- compoundexecutedA Growth-Earmarked Treasury Strategy for Compound63%
- compoundexecutedCompound <> Morpho <> Polygon Collaboration62%
- compoundexecutedDelegate COMP Yield Strategy tokens to the Compound Foundation57%