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]: Unable to cancel unbonding delegation of jailed validators #19279

Closed
1 task done
anilcse opened this issue Jan 29, 2024 · 3 comments · Fixed by #19415
Closed
1 task done

[Bug]: Unable to cancel unbonding delegation of jailed validators #19279

anilcse opened this issue Jan 29, 2024 · 3 comments · Fixed by #19415
Assignees
Labels

Comments

@anilcse
Copy link
Collaborator

anilcse commented Jan 29, 2024

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

I tried to cancel an unbond delegation from jailed validator, it is failing with error failed to execute message; message index: 0: validator for this address is currently jailed. I don't see any supporting description in the requirements to consider this as an expected behaviour.

Cosmos SDK Version

0.47, 0.50, main

How to reproduce?

  • Undelegate from jailed validator
  • Cancel unbonding delegation
@anilcse anilcse added the T:Bug label Jan 29, 2024
@alexanderbez
Copy link
Contributor

Unclear if this is expected behavior or not. Need to dig up the original PR and see what the context was.

@likhita-809
Copy link
Contributor

In the original implementation of cancel unbonding delegation, we intended to return error on cancel unbonding delegation for jailed validator. Although I couldn't find any description describing this behaviour. Either we should make clear docs on this or add a feature supporting this issue.
https://github.com/cosmos/cosmos-sdk/pull/10885/files#diff-5ea92aa6ab2a6d865b7641169f4a530e3ec4121e427e4bc292666fec403244daR423-R425
cc: @alexanderbez

@likhita-809 likhita-809 self-assigned this Feb 6, 2024
@alexanderbez
Copy link
Contributor

Personally, I would like to see a strong case to be made to support this feature.

Otherwise, we should just update documentation to make it clear that this is NOT supported. WDYT @likhita-809?

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