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

[EPOCH TRANSITION] - Membership trait has an additional method to fetch a stake table for a given epoch #3726

Open
lukaszrzasik opened this issue Oct 3, 2024 · 0 comments · May be fixed by EspressoSystems/espresso-sequencer#2237

Comments

@lukaszrzasik
Copy link
Contributor

What is this task and why do we need to work on it?

This is required to implement a variable stake table. Stake table can change while transitioning from one epoch to the next. Looking at it from a different angle: there are multiple stake tables, one per epoch.

We need an additional method that fetches a new stake table for the given epoch. This method should be stubbed in HotShot. The real stake table is to be fetched from a contract in L1. This issue should have a corresponding issue in sequencer project in which the method is implemented.

Epoch transition details can be found here: https://www.notion.so/espressosys/Epoch-transition-without-extra-types-and-with-last-votes-broadcast-1112431b68e98092a47aea71b41bec8c

What work will need to be done to complete this task?

No response

Are there any other details to include?

No response

What are the acceptance criteria to close this issue?

The Membership trait has an additional method that fetches a stake table for the given epoch. This method should be stubbed in HotShot.

Branch work will be merged to (if not the default branch)

No response

@ss-es ss-es modified the milestones: Stake table update (PoS), Upgrade (PoS), Epochs (PoS) Oct 21, 2024
@ss-es ss-es removed this from the Stake table update (PoS) milestone Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants