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

Epochs: Introduce the last-epoch validator set #1650

Closed
Tracked by #1516
insumity opened this issue Feb 20, 2024 · 0 comments · Fixed by #1660
Closed
Tracked by #1516

Epochs: Introduce the last-epoch validator set #1650

insumity opened this issue Feb 20, 2024 · 0 comments · Fixed by #1660
Assignees
Labels
C:x/provider Assigned automatically by the PR labeler S: NewThings Work towards your business objectives with new products, features, or integrations

Comments

@insumity
Copy link
Contributor

insumity commented Feb 20, 2024

Problem

Currently, we cannot move to an epoch-based approach as is because key-assignment replacements work on a per-block basis. To tackle this, we intend to store the last validator set that was sent to a consumer chain at the last epoch. This way, we could easily create ValidatorUpdates to send down to the consumer chains.

Closing criteria

  1. Introduce the relevant state and getter/setters
  2. (optional) Move soft-opt-out to only set the 95% top validators. The implication of this would be that the validators that opted out would still get rewards but the consumer chain would be faster because we won't have rounds with non-existent proposers.
  3. Add a test that would check that we only send VSCPackets once every BlocksPerEpoch (see Epochs: Introduce governance param #1649).
@insumity insumity added the status: waiting-triage This issue/PR has not yet been triaged by the team. label Feb 20, 2024
@github-project-automation github-project-automation bot moved this to 🩹 F1: Triage in Cosmos Hub Feb 20, 2024
@insumity insumity added C:x/provider Assigned automatically by the PR labeler S: NewThings Work towards your business objectives with new products, features, or integrations and removed status: waiting-triage This issue/PR has not yet been triaged by the team. labels Feb 20, 2024
@insumity insumity moved this from 🩹 F1: Triage to 🏗 F3: InProgress in Cosmos Hub Feb 20, 2024
@insumity insumity mentioned this issue Feb 27, 2024
21 tasks
@insumity insumity moved this from 🏗 F3: InProgress to 👀 F3: InReview in Cosmos Hub Feb 29, 2024
@insumity insumity self-assigned this Feb 29, 2024
@mpoke mpoke linked a pull request Feb 29, 2024 that will close this issue
21 tasks
@insumity insumity moved this from 👀 F3: InReview to ✅ Done in Cosmos Hub Mar 7, 2024
@github-project-automation github-project-automation bot moved this from ✅ Done to 👍 F4: Assessment in Cosmos Hub Mar 12, 2024
@mpoke mpoke moved this from 👍 F4: Assessment to ✅ Done in Cosmos Hub Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:x/provider Assigned automatically by the PR labeler S: NewThings Work towards your business objectives with new products, features, or integrations
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant