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

Opted in validators do not get jailed twice #1751

Closed
p-offtermatt opened this issue Apr 3, 2024 · 1 comment
Closed

Opted in validators do not get jailed twice #1751

p-offtermatt opened this issue Apr 3, 2024 · 1 comment
Assignees
Labels
S: NewThings Work towards your business objectives with new products, features, or integrations source: devnet To indicate an issue surfaced in a devnet. type: bug Issues that need priority attention -- something isn't working

Comments

@p-offtermatt
Copy link
Contributor

Problem

When they already were jailed, it seems opt-in validators sometimes do not get jailed again after they unjail and commit another downtime infraction.

Problem details

Steps to reproduce

  1. Sync consumer node with a non-top N validator
  2. Opt-in
  3. Stop consumer node, get jailed
  4. Sync consumer node again
  5. Submit unjail tx in provider chain
  6. Stop consumer node a second time- validator does not get jailed [Validator still shows up in tendermint-validator-set for both provider and top-N consumer]
@p-offtermatt p-offtermatt added type: bug Issues that need priority attention -- something isn't working source: devnet To indicate an issue surfaced in a devnet. labels Apr 3, 2024
@p-offtermatt p-offtermatt self-assigned this Apr 3, 2024
@github-project-automation github-project-automation bot moved this to 🩹 F1: Triage in Cosmos Hub Apr 3, 2024
@p-offtermatt p-offtermatt moved this from 🩹 F1: Triage to 🏗 F3: InProgress in Cosmos Hub Apr 3, 2024
@p-offtermatt p-offtermatt added the S: NewThings Work towards your business objectives with new products, features, or integrations label Apr 3, 2024
@p-offtermatt
Copy link
Contributor Author

This was not an issue, but just happened due to slash-throttling; #1752 adds a test for the scenario

@github-project-automation github-project-automation bot moved this from 🏗 F3: InProgress to 👍 F4: Assessment in Cosmos Hub Apr 8, 2024
@mpoke mpoke moved this from 👍 F4: Assessment to ✅ Done in Cosmos Hub Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S: NewThings Work towards your business objectives with new products, features, or integrations source: devnet To indicate an issue surfaced in a devnet. type: bug Issues that need priority attention -- something isn't working
Projects
Status: ✅ Done
Development

No branches or pull requests

1 participant