Open ryu9827 opened 6 years ago
Because security of the contract is our most concerned. As each single owner has too much equal authority (like add owner, set operator and set minter, then fully control these two contract), we suggest adding more security logic, like sigature mechanism, to make sure those key functions are confirmed by multiple owners instead of single owner.
I have a lot of questions in this regards:
And more questions: Did you think about what the _wallet variable means in the stake.sol constructor? Could it be related somehow to some multisig wallet? Yes, we don't know, but it could be. Probably we should ask the question to the LEVERJ.IO development team?
On more thing...
Bruce, I think it is better to create many issues, not just one like "There are many problems in the code, including, a).. b)... c)... ".
It is a good practice to keep each one specific about only one problem.
Then we can report, discuss, fix, check, confirm and / or close each issue separately.
Thanks.
Thanks for providing the advise. The reason I packed these questions into one issue is just they are all about system administration authority.
@ryu9827 @tikonoff I agree with this issue. I never feel too comfortable with superadmin's scenarios (even in my own computer). But it's not a critical issue according to the scale that we use. I would categorize this as Major
Sure, we struggle with the priorities and decided to discuss it later with Matthew. Btw, please have a look at the new report on Slack.
Single owner has far too much power, add new owner and remove other owners. This is not good practice and carries significant risk for the app. Suggest to add multiple signature for improving security.