Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use an upgradable pattern for the external modules #30

Open
akolotov opened this issue Mar 9, 2021 · 0 comments
Open

Use an upgradable pattern for the external modules #30

akolotov opened this issue Mar 9, 2021 · 0 comments
Labels
deployment related to the deployment process enhancement New feature or request external modules Related to contracts which are external w.r.t. to the omnibridge contracts

Comments

@akolotov
Copy link
Collaborator

akolotov commented Mar 9, 2021

Currently there are three modules serving some aspects of the bridge contracts configuration:

  • the fee manager
  • the gas limit manager
  • the forwarding rules manager

These modules are implemented as a separate contracts and the bridge contract calls the modules' methods to get/store some information.

During the bridge usage the modules could collect lots of configuration data. But if an issue is found in the code of the modules they need to be updated. Since current contracts of the modules do not support the upgradable pattern, it means that the bridge admins could be required to perform lots of transactions to migrate the state from the old version of the module to the new one.

@akolotov akolotov added enhancement New feature or request deployment related to the deployment process external modules Related to contracts which are external w.r.t. to the omnibridge contracts labels Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployment related to the deployment process enhancement New feature or request external modules Related to contracts which are external w.r.t. to the omnibridge contracts
Projects
None yet
Development

No branches or pull requests

1 participant