bench32Prefixes donnot change。

[elvin-du]

Summary

bench32Prefixes donnot change.

I have changed prefixes using SetBech32PrefixForAccount(),SetBech32PrefixForValidator(),SetBech32PrefixForConsensusNode()method, but gaiacli keys parse command cannot use new prefixes.

for example:
I made the following changes to the gaiacli code. new gaiacli can generate addresses prefixed with mdk, But when using the gaiacli keys parse command, the cosmos prefix is still generated.

func main() {
	// Configure cobra to sort commands
	cobra.EnableCommandSorting = false

	// Instantiate the codec for the command line application
	cdc := app.MakeCodec()

	// Read in the configuration file for the sdk
	config := sdk.GetConfig()
	config.SetBech32PrefixForAccount("mdk", "mdkpub")
	config.Seal()
.....
}

Problem Definition

Proposal

---

For Admin Use

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

[alexanderbez]

re-opening. ref: #5283

We should remove the (private) global singleton in favor of creating a config each time. This will probably solve the race condition(s).

[alessio]

We should form the singleton thing into a new issue @jackzampolin

[njmurarka]

Can we please have a stable bugfix for this in master for 0.38? We are stuck with the same problem...

[gsora]

Yes please! Can we have this backported to 0.38?

[alessio]

It only takes to backport 4e328d7, so yes. I'd you will have it in the next 0.38.5 stable release.

@alexanderbez @clevinson what tag should we use to avoid losing track of this when we'll prepare the next 0.38 patch release?

[njmurarka]

Any idea when 0.38.5 will be happening?

[alexanderbez]

@alessio living backport branches. Please create a cherry-pick/backport PR to backport/release/v0.38.x (which I've already pushed).

[alessio]

@njmurarka @gsora mind testing your applications against this commit? 6e3d826

[njmurarka]

@njmurarka @gsora mind testing your applications against this commit? 6e3d826

Still a problem in 0.38.5.

I am told this will be fixed in 0.39.0.

[alessio]

Yes, #6340 addresses this and shall be relased with v0.39.0