Interop: Add new role for dependency set management

[tynes]

Overview

The SystemConfigInterop contract manages the interop dependency set. Right now the owner of the SystemConfig can add and remove dependencies. The owner of the SystemConfig is considered the chain operator. We want to allow for a different role to manage the dependency set so that in production the dependency set can be managed by governance rather than the chain operator.

Definition of Done

• Specs are updated with this new role
  • Could follow this spec, how there is a "Functions" header and subheaders for each function
  • What should this role be called?
• Source code is implemented
• Full test coverage

[AmadiMichael]

The intention here is to have only one authorized caller of each of the 2 functions at a time right? e.g addDependency cannot have multiple authorized callers at once...

[tynes]

Yes exactly, just 1 account that can call addDependency/removeDependency that MAY or MAY NOT be different than the owner from Ownable. Then for the standard config definition, the account that can add remove dependencies MUST be the foundation multisig

[AmadiMichael]

Ah yes thanks, was about to ask that now,
where can i find the foundation multisig address?

[tynes]

You can see in the docs here although we do not want to hardcode any addresses, it would be an argument to initialize at deploy time

[AmadiMichael]

You can see in the docs here although we do not want to hardcode any addresses, it would be an argument to initialize at deploy time

will this be modifiable and if so, by whom?