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

Write contract upgrade strategy ADR for settlement hub #5

Open
mattdf opened this issue Jan 10, 2022 · 0 comments
Open

Write contract upgrade strategy ADR for settlement hub #5

mattdf opened this issue Jan 10, 2022 · 0 comments

Comments

@mattdf
Copy link

mattdf commented Jan 10, 2022

The set of contracts in the settlement hub will not be static and never changed, added to or upgraded, hence a strategy needs to be decided on to perform protocol upgrades.

There are several options that can be implemented, and multiple could be supported for different deployments:

  • Whitelist a multisig address on-chain that is deployed at genesis, which is the only one that can perform upgrades
  • Use/implement cosmos governance module in optimint and leverage that to signal that a new client should be downloaded with a different contract set
  • In the case of the settlement hub having multiple validators & a staking mechanic (either directly or via something like interchain security), the set of valid rollup contracts can be decided and whitelisted by validator majority
@mattdf mattdf moved this to TODO in Celestia Node Jan 12, 2022
@tzdybal tzdybal removed this from Celestia Node Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant