fluidkey
Create multisig for `walletbeat.eth`
This issue tracks the work of creating a Safe wallet and moving the walletbeat.eth ENS name to be owned by the multisig. The multisig itself can be a 1-of-1 until the full set of signers is determined, with the goal that we have at least 5 distinct entities represented on it.
The beta.walletbeat.eth ENS subdomain may remain in place so that CI can to continue to update its records unimpeded.
Current candidates who have committed to be on the multisig:
- @nconsigny (EF)
- @lucemans (EF)
- @polymutex (independent)
- @PatrickAlphaC (independent)
This is currently an insufficient size for actual decentralization, especially given that this would mean 2/4 (50%) Ethereum Foundation ownership. I think having 2/5 (i.e. 40%) Ethereum Foundation ownership might be OK, but anything over 49% means Walletbeat is effectively an arm of the EF. Which would not be a bad outcome, don't get me wrong! I think the EF would be the best possible steward foundation that this project could ask for, if the project is to have one. But I'd like to see if we can decentralize this further first. :)
As possible additional candidates for multisig:
- @darrylyeo (interested but not certain yet)
- @Hugoo
- @mozrt2
Please chime in here if you would like to commit to be on the multisig. Responsibilities include:
- Being responsive and diligent for multisig transaction signing requests, ideally turnaround within 24h >75% of the time.
- Some non-zero level of long-term commitment to and involvement within the project, especially (1) decisions around the wallet attribute set, and (2) meta-decisions around governance changes.
- A commitment that you are not currently affiliated with any wallet development entity which works on a wallet that Walletbeat reviews. If this were to change in the future, you would be expected to be transparent about this and to relinquish your role, unless other governance members determine that such an affiliation would not be of significant concern.
- A commitment to finding and nominating a suitable replacement for your own role if you were to relinquish this responsibility in the future.
I'm on a few security councils with very low SLAs (1-hour SLAs), so turnaround is not a problem for me, especially for security-related events.
Volume might be though. If we are sending several transactions a week, I might not be the right person for this.
If it's a couple a month, I'd be honored to be selected here.
Volume might be though. If we are sending several transactions a week, I might not be the right person for this.
I don't think it would be so high-volume, other than an initial one-time burst to set this all up. In the steady state, I imagine the only types of requests would be around:
- Multisig membership changes, hopefully rare, a few a month at most?
- Recovery in case CI's EOA private key (which has the authority to change
walletbeat.eth'scontentHashrecord, in order to deploy new versions of the walletbeat website) gets compromised. That should hopefully not happen, but if it does happen, it does require a fast turnaround time.
I expect the bulk of the assignment here is more around general and consistent time commitment to Walletbeat as a project.
If it's a couple a month, I'd be honored to be selected here.
I'd be honored for you to be on it :)
The multisig now exists on mainnet and has been seeded with the initial grant funds. If you'd like to be added to the multisig, let me know your address.