-
Notifications
You must be signed in to change notification settings - Fork 100
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
Can't undelegate: "invalid Bech32 prefix; expected cosmos, got cosmosvaloper" #1517
Labels
bug 🐛
issues related to unhandled errors in the code that need to be fixed
Comments
NodeGuy
added
bug 🐛
issues related to unhandled errors in the code that need to be fixed
staking1
labels
Nov 5, 2018
Can't replicate this. You're sure you did |
Oh. It does undelegate, but another request (GET http://localhost:9070/stake/delegators/cosmosvaloper1qnqck57r07m82p2p2062trdjx6jh329ndcwcla/delegations/cosmosvaloper1qnqck57r07m82p2p2062trdjx6jh329ndcwcla) is failing. |
This was referenced Nov 6, 2018
Closed
This was referenced Nov 13, 2018
This was referenced Jan 16, 2019
This was referenced Feb 14, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
UI Version: 03067df
Description:
local
account.A notification reports success but the undelegation fails:
The HTTP response is
invalid Bech32 prefix; expected cosmos, got cosmosvaloper
.The text was updated successfully, but these errors were encountered: