The goal of this proposal is to modify the current multisig appointed in [WIP #21].
- Modify the multisig members based on legal consultation.
- Improve the multisig efficiency.
- Yes, implement the changes
- No, don’t implement the changes
As a result of WIP #28 and WIP #30, five officers have been appointed to Wonderland Core Team.
As a recommendation to reduce liability on core team members, they should not hold another sensitive position to the protocol’s security.
It is also recommended that Wonderland refrains from publicly doxing the individuals participating in the multisig, as it is not a paid position and the DAO does not cover potential security issues nor the costs to limit the risks that may arise due to this role.
In order to achieve the objectives above, here is what is being proposed:
- Remove @NalX from the multisig
- Will be removed after the new signers have been added.
- Add two new members to the multisig
- One neutral party and one community member with no official or unofficial role in Wonderland (e.g. officers, treasury operators, moderators).
- Keep the multisig requiring three signatures to execute transactions (3/6).
- This aims at improving execution time while sacrificing limited security.
The team has already identified two additions experienced in working with a multisig. One of them has extensive knowledge that will be useful to create complex transactions when required. This is something that current signers could not always cover and had to ask the Technical Officer for assistance. Both can read and verify the needed information, are diligent and active daily. Activity times (timezone) overlap with existing signers, so establishing an organized structure with an additional member will ensure fast and frictionless execution times.
Before anyone is added to the multisig, they will be internally doxxed to the Operations Officer. The Operations Officer will verify their identities and background and make sure they are not affiliated with other protocols that would create a conflict of interest. The data will be encrypted and given to the legal department, for additional security and accountability.
These changes will improve the efficiency of the multisig, which is currently sub-optimal, while adding another layer of security and keeping identities protected.
If this passes, the new members will be added to all multisig and communication channel. Once it is done, Nal X will be removed.
Since an RFC is a “work in progress” Proposal, not all of these points need to be filled out from the beginning. They can be added over time as the RFC evolves into a mature Proposal.