Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Group draft-proposal, delegate msg, validator address comes back as "invalid Bech32 prefix" #16307

Closed
gjermundgaraba opened this issue May 26, 2023 · 0 comments · Fixed by #16312
Assignees
Labels

Comments

@gjermundgaraba
Copy link
Contributor

Summary of Bug

When using the group draft-proposal functionality and trying to delegate, the CLI UI incorrectly expects a non-valoper Bech32 prefix: "invalid address: invalid Bech32 prefix; expected xxx, got xxxvaloper"

Version

0.47.2

Steps to Reproduce

Example:

➜  group_testing empowerd tx group draft-proposal
✔ other
✔ /cosmos.staking.v1beta1.MsgDelegate
Enter proposal's title: Delegate to X
✔ Enter proposal's authors: empower1m9l358xunhhwds0568za49mzhvuxx9uxl4sqxn█
✔ Enter proposal's summary: delegate yo█
Enter proposal's details: plz
Enter proposal's proposal forum url: https://so-many-questions.com
Enter proposal's vote option context: si o no
Enter group policy address: empower17l6djqrztw0ux668vkw7ff7d2602jvml52w9fyrvryusp7djnhfq8anafu
Enter proposer address: empower1m9l358xunhhwds0568za49mzhvuxx9uxl4sqxn
Enter msg's delegator address: empower17l6djqrztw0ux668vkw7ff7d2602jvml52w9fyrvryusp7djnhfq8anafu
✗ Enter msg's validator address: empowervaloper1xm30kmu6gezca96ksmk8ketfg47zdvt9jmrham█
>> invalid address: invalid Bech32 prefix; expected empower, got empowervaloper

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants