Closed Segfaultd closed 1 year ago
It seems to me from https://github.com/cosmos/cosmos-sdk/issues/13314#issuecomment-1249936670 that the old and new binaries are using different values of the bech32 prefix. @Segfaultd Could you check that they are the same?
Hello @amaurym and thank you for your comment.
You can see here that the prefixes used at Lum Chain weren't changed for the last 13 months. https://github.com/lum-network/chain/blob/master/app/prefix.go
But we have a custom coin type. Dunno if that could have an impact or not.
Have you been able to resolve your issue?
Hi @julienrbrt
Yes, the fix was to call SetConfig in app.go as well (since it was registered only on CLI entrypoint at first) https://github.com/lum-network/chain/commit/d9afc2595d4436a177ced5c664929004d3e3e8a8#diff-0f1d2976054440336a576d47a44a37b80cdf6701dd9113012bce0e3c425819b7R165
Summary of Bug
When trying to upgrade our empty testnet to Cosmos SDK 0.46.6, the upgrade fails on migrating the auth module. W've been extensively reviewing our changes, and we followed every upgrade procedure from the official Cosmos SDK documentation.
Is there any thing to know or to do to be able to pass that upgrade ?
That's a duplicate issue of #13314 but the issue was closed without explicitely stating what was the solution.
Version