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

virtual-staking: Unbonding from tombstoned validators #154

Closed
Tracked by #85
maurolacy opened this issue Oct 24, 2023 · 0 comments · Fixed by #201
Closed
Tracked by #85

virtual-staking: Unbonding from tombstoned validators #154

maurolacy opened this issue Oct 24, 2023 · 0 comments · Fixed by #201

Comments

@maurolacy
Copy link
Collaborator

maurolacy commented Oct 24, 2023

When unbonding from a tombstoned validator, we need to make sure if there's the need to unbond funds from the blockchain staking module or not. This is because some blockchain implementations may decide to unbond automatically when tombstoning, and after slashing, a validator.

This would require:

  • Knowing that a validator is tombstoned. Currently we have a inactive list in virtual-staking, which doesn't differentiate between jailed, unbonded or tombstoned validators. Let's add a state to the list, so that we can check this. Alternatively, we can simply do the bonded check below for all inactive validators.
  • Checking the bonded amount a tombstoned / inactive validator has. This has to be done against the blockchain, using the StakingQuery::Delegation message (or the query_delegation helper), in order to send an Unbond message only if / when needed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant