Problem: Partner nodes are outdated

[outerlook]

No description provided.

[MicBun]

For references: #534 (comment)

[MicBun]

Hi @outerlook, it is a suggestion from me.
How about separating this PR #534 into two?

Let's isolate any upgrade related to go.mod and code related to it into a separate PR. That way, we can continue working on other things that do not require node upgrades. Node upgrade requires a reset from all instances including external parties that have been joined.

@truflation/team-tsn-kwil please leave a comment here about upgrading nodes if there is a safer way to upgrade it or any best practices for it.

[outerlook]

Hey @MicBun, as I currently understood, this wouldn't require a full reset, just a gracefully update. I.e. they and us will just replace the binaries, because there's no breaking change to the block chain data.

We would just update the image that powers tsn on our side

[outerlook]

We would just deploy the new contracts (which require the changes) after everyone got the right version, but until there we can work on other things as normal

[MicBun]

Just a gracefully update. I.e. they and us will just replace the binaries, because there's no breaking change to the block chain data.

We would just update the image that powers tsn on our side

Glad to hear that. So in this case.

1. Upgrade node first.
2. Tell them to upgrade too.
3. Upgrade the contract.

[outerlook]

Exactly! Then we would have no disruption

[outerlook]

won't update nodes anymore until a new kwil release to get more at once. context: #441 (comment)