Skip to content

fix(scripts): adapt upgrade-node.sh to SDK v0.50#342

Draft
tbruyelle wants to merge 1 commit into
atomone-hub:mainfrom
tbruyelle:tbruyelle/fix/upgrade-node-script-sdk50
Draft

fix(scripts): adapt upgrade-node.sh to SDK v0.50#342
tbruyelle wants to merge 1 commit into
atomone-hub:mainfrom
tbruyelle:tbruyelle/fix/upgrade-node-script-sdk50

Conversation

@tbruyelle

Copy link
Copy Markdown
Collaborator

Description

Adapts contrib/scripts/upgrade-node.sh to the SDK v0.50 bump (v4 upgrade):

  • config command now requires the set client <key> <value> form
  • q gov proposal output nests the proposal under .proposal and wraps Any messages in a value field
  • status output keys are now snake_case (sync_info instead of SyncInfo, see feat(cli): status cmd cli support output text cosmos/cosmos-sdk#17184)
  • Set the dynamicfee fee denom to uphoton in genesis so photon fees can be resolved

⚠️ Keep in draft until the v4 upgrade

This script tests the upgrade path by starting a localnet with the previous binary (ATOMONED_BIN) and upgrading to the new one (ATOMONED_NEW_BIN). These changes assume the previous binary is already on SDK v0.50, which will only be true once mainnet has effectively upgraded to v4. Merging before that would break the script for the current v3 → v4 upgrade testing flow.

- `config` command now requires the `set client <key> <value>` form
- `q gov proposal` output nests the proposal under `.proposal` and wraps
  Any messages in a `value` field
- `status` output keys are now snake_case (`sync_info` instead of
  `SyncInfo`, see cosmos/cosmos-sdk#17184)
- set dynamicfee fee denom to uphoton in genesis so photon fees can be
  resolved
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

Successfully merging this pull request may close these issues.

1 participant