Feature description

Currently, Cosmos chains that Juno supports may be using the x/upgrade module in order to perform seamless on-chain upgrades from one binary version to the other. Due to the fact that a new binary version might present breaking changes, Juno operators need to remember when those upgrade happen and quickly replace the Juno binary with the new version that supports such changes. As more and more chains are managed by the same operator, handling such upgrades will be harder and harder.

To solve the problem, we should allow Juno to react to on-chain upgrades when they happen in a reactive way (only after the upgrade happened successfully).

Implementation proposal

One idea might be to leverage the x/upgrade itself: one an on-chain upgrade proposal passes, the upgrade details will be stored on the chain itself. Such details include also the upgrade height. What we could do is leveraging that upgrade height and the corresponding upgrade name to make sure that Juno panics when such upgrade happens. This, combined with something like Cosmovisor should make it fairly easy to implement a way to switch from one Juno binary to another after an on-chain upgrade is successful.