DualOwnableUpgradeable

[salieflewis]

Overview

The protocol is initialized with two admins. One is a trusted operator or team of operators who are given access in order to continue moving quickly to enhance the protocol. The other is the DAO (or other assigned operator) which reserves the highest level of ownership rights of the protocol. While both parties have admin access at the beginning, the DAO has the sole ability to revoke the access of the other party at any point.

Questions

1. Should the DAO be able to change the address of the other permissioned operator?
2. Should the DAO be able to reinstate a second permissioned operator after it has already been revoked?

[salieflewis]

Hi @0xTranqui. I hope you don't mind me moving this conversation over here, and changing some of the language from your Figma post. I think the diagram you introduced there should find its way here also!

How do you feel about the term permissioned operator? Maybe it just makes sense to use what you've written at the Solidity level, and refer to each party as the owner and secondOwner. Let me know if you want me to edit/add anything in the post above.

I think it makes sense to think of these actions in the context of the DAO structure we're building it in. A one step transaction to either revoke ownership from the secondOwner or transfer ownership to a new secondOwner makes sense to me.

I don't see why a check against reinstating a secondOwner that historically had permissions would be necessary. But curious as to what your thoughts are on that!