celestia-specs icon indicating copy to clipboard operation
celestia-specs copied to clipboard

Published 20 hours ago • verified publisher icon celestiaorg

Define upgrade and fork activation mechanism

Open adlerjohn opened this issue 4 years ago • 3 comments

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 avatar Feb 18 '21 14:02 adlerjohn

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 avatar Feb 18 '21 17:02 liamsi

ref: https://github.com/lazyledger/lazyledger-specs/issues/171

liamsi avatar May 31 '21 09:05 liamsi

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

liamsi avatar Dec 08 '21 18:12 liamsi