Need to set and upgrade bech32ibc -> nativeHRP to "umee" in genesis.json for calypso

[brianosaurus]

Summary

nativeHRP needs to be set when we upgrade the gravity bridge

Problem Definition

Because we aren't properly setting nativeHRP, we are receiving gravity bridge errors. Make it so that is properly set in either app.go or in genesis.json and upgraded in an upgrade handler when we move to mainnet.

Proposal

The best solution would be to initialize the bech32ibc handler in app.go to set the nativeHRP however that may not be possible. The second choice is to use the upgrade handler to ensure the correct value is in genesis.json and within the bech32ibc keeper.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[robert-zaremba]

What is nativeHRP? Why we need it for Calypso? Why this is working in Umeemania?

[brianosaurus]

Good questions. HRP (human-readable part) a new thing introduced by Osmosis to (in @facundomedica's words):

Are you trying to sync using the latest umee binary? I think that’s the issue, because the HRP thing is a new thing in the latest GB. Because what happened before if you sent tokens to an account with a different prefix (for example osmo1… instead of umee1…) is that the account would get converted to the local prefix and the tokens sent. That way you wouldn’t lose tokens if you’d sent them to the incorrect prefix. But now we can pass gov proposals to “attach” a prefix to an IBC channel, that way you can bypass Umee and send tokens directly from Ethereum to any other cosmos chain. In case any errors arise, tokens will go to the converted native account

We receive invalid HRP errors periodically. It's because our chain has "osmo" for the native HRP which is wrong.