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

Valset update: validator state #118

Closed
maurolacy opened this issue Aug 31, 2023 · 0 comments · Fixed by #148 or #153
Closed

Valset update: validator state #118

maurolacy opened this issue Aug 31, 2023 · 0 comments · Fixed by #148 or #153
Assignees

Comments

@maurolacy
Copy link
Collaborator

maurolacy commented Aug 31, 2023

As a follow-up of #109, let's change valset updates to support validator status (active, unbonded, jailed, tombstoned).

The list of states comes from https://hub.cosmos.network/main/validators/validator-faq.html#what-are-the-different-states-a-validator-can-be-in.

We can have:

  • active: In validator set.
  • unbonded: Not in validator set, because of not enough bonded assets.
  • jailed: Not in validator set, because of misbehaviour.
  • tombstoned: Permanently not in validator set, because of misbehaviour.

This may be used during cross-unbonding; so that we know if we need to apply the unbonding period or not.
It can also be checked during cross-bonding, to prevent bonding to tombstoned validators.

Note: This may be difficult to implement with the current impl, as the valset updates use CRDT for consistency over unordered channels.

@maurolacy maurolacy changed the title Valset update validator state Valset update: validator state Aug 31, 2023
@maurolacy maurolacy self-assigned this Sep 1, 2023
@maurolacy maurolacy mentioned this issue Sep 25, 2023
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant