[Bug]: Unbond validator is not working on v19.0.0-rc

[arifintahu]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

A bug happened!
I tried gaiad tx staking unbond-validator --from validator1 on v19.0.0-rc0 theta testnet and then I got

Error: hrp does not match bech32 prefix: expected 'cosmos' got 'cosmosvaloper': internal logic error

After following the corresponding code, it seems the error come from cosmos sdk v0.50.8-lsm https://github.com/cosmos/cosmos-sdk/blob/62baa29ab9e3f190b148fc9e2e8e884da452a8e9/x/staking/client/cli/tx.go#L338
valAddrCodec.BytesToString cannot process valoper

Gaia Version

v19.0.0-rc0 to v19.0.0-rc3

How to reproduce?

1. create validator on theta testnet
2. unbond validator gaiad tx staking unbond-validator --from validator1

[MSalopek]

Thanks for opening the issue.

The text and the image you showed do not match. The text states you are executing an unbond Tx, while the image shows that you have a signing step.

How did you generate the Tx?

We're checking it out.

[arifintahu]

I tried two methods directly signing unbond validator and signing using tx sign, but the result is the same

1. gaiad tx staking unbond-validator --from validator1
2. gaiad tx staking unbond-validator --from validator1 --generate-only > msg.json | gaiad tx sign msg.json --from validator1

[MSalopek]

Thanks for the additional context!

We are looking into it.

[MSalopek]

The bug has been triaged and the fix will be ready soon. The fix will be a part of the upcoming cosmos-sdk-lsm release and the next gaia release candidate.

Thank you @arifintahu

[MSalopek]

Fixed in:
#3249

Targeting v19.0.0-rc0. The changes will be in the mainnet v19.0.0 release.

Thanks once again!

[arifintahu]

Great, glad to hear that!