Migrate WBTC big DAO multisig to a new one with safer active signers #12
Conversation
This comment was marked as duplicate.
This comment was marked as duplicate.
|
this is great to hear, thank you @tranvictor |
Change B.Protocol/RiskDAO to RiskDAO in the list of DAO memebers
|
One question that came to my mind - it is possible to add / remove / replace existing signers:
Since the new mulisig has been deployed + all the verification tweets were sent = my comment now is irrelevant 🤡 For the historical context (blockchain archeologists) why deploying new multisig if changing old is possible? Or maybe it is not?
Diminish as in "reduce redundancy" or diminish as in "we are completely f***ed up"? |
|
@marsrobertson changing one by one of the old multisig is possible, however it takes huge effort for the whole DAO to vote on. The multisig doesn't allow batch modification, each We are fine. Not fked in any ways. |
|
Hello can we please get an update on what's happening with this PR ? |
|
any update on this please ? |
|
@tranvictor pls include my issue with this PR thank u so much in advance. @ravz thank u for the support. |
|
any update on this pls? thank u in advance. |
|
hello @tranvictor WBTC DAO, pls help return my 0.04495 WBTC |
|
any update on this please :( Transaction hash: 0x1f1c8971dec959d38bcaa5606eb474d028617752240727692cd5ef21a435d847 |
|
@tranvictor thanks for the update. |
|
hello, kindly let us know any update on this. thank you. |
|
hi any update please? |
|
Tom Bean lost the keys to his entire protocol, why the fuck would he be put on here? #BearishWBTC |
Issue
The current big DAO multisig (
0xd409db68d0e6e97e1cb1f3eb0bd38de278bc3c68) has 18 signers and requires 11 to form a consensus and process a transaction. Now that nearly 4 years have passed, several of the original signers have become inactive and/or lost control of their keys which diminishes the availability of the multisig. It’s important that we are able to successfully process a vote in the event that any of the WBTC contract(s) needs be amended (replace custodian, upgrade/modify token contract, etc.).Solution
As a result, we are migrating the WBTC Big DAO (whose chief responsibility is to govern the Controller) to a new multi-sig contract with new members and an updated voting threshold. Here is a summary of the changes:
Old Big DAO Multi-sig: 0xd409db68d0e6e97e1cb1f3eb0bd38de278bc3c68 will be deprecated.
New Big DAO Multi-sig: 0xB33f8879d4608711cEBb623F293F8Da13B8A37c5
Previous members (18 seats, 11 votes required):
New Members (13 seats, 8 votes required):
New Member Address Verification Tweets:
What’s included in this Pull Request:
2.1. Kyber initiated with this transaction. The
transactionIDis 92.2. All required approvals are done
3.1. Bitgo initiated with this transaction. The
transactionIDis 03.2. All required approvals are done