Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

Define upgrade and fork activation mechanism #128

Open
adlerjohn opened this issue Feb 18, 2021 · 3 comments
Open

Define upgrade and fork activation mechanism #128

adlerjohn opened this issue Feb 18, 2021 · 3 comments
Labels
investigation Investigation required.

Comments

@adlerjohn
Copy link
Member

adlerjohn commented Feb 18, 2021

To avoid future messes, we should define a mechanism to deploy upgrades (i.e. hard forks, and potentially also soft forks).

https://github.com/cosmos/cosmos-sdk/blob/b4820fe491e91cd95340f2f7b606adab454a7636/x/upgrade/spec/README.md

https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki

@adlerjohn adlerjohn self-assigned this Feb 18, 2021
@adlerjohn adlerjohn changed the title Define upgrade mechanism Define upgrade and fork activation mechanism Feb 18, 2021
@liamsi
Copy link
Member

liamsi commented Feb 18, 2021

I'm definitely in favor of using the Cosmos-SDK upgrade module, if feasible. Even if that means some tradeoffs.
https://github.com/cosmos/cosmos-sdk/blob/master/x/upgrade/spec/01_concepts.md

Otherwise, it will cost us time spec this out and implement/execute this correctly. Or, there be dragons 🐲

@liamsi
Copy link
Member

liamsi commented May 31, 2021

ref: #171

@liamsi
Copy link
Member

liamsi commented Dec 8, 2021

This is still relevant independent of the specs we need to make a decision here and have a proper plan.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
investigation Investigation required.
Projects
No open projects
Status: No status
Development

No branches or pull requests

2 participants