-
Notifications
You must be signed in to change notification settings - Fork 94
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
Add proposed Sepolia Capella epoch #30
Conversation
Signed-off-by: Tim Beiko <t.beiko23@gmail.com>
Co-authored-by: terencechain <terence@prysmaticlabs.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will wait for more 👍🏼s before merging this
On protest, but given the boundary condition that we decided to go with the fork anyway, the epoch is 👍 |
Looks good to me 👍 |
Looks good |
The changes match the merged metadata in the official Sepolia repo: eth-clients/sepolia#30
At the time of updating, what should I do as I'm running a few Sepolia test net nodes. download the new Sepolia image and that's all? |
Yes, from a node runner perspective - all you need to do is update to the latest release of the client you are using |
Proposed based on the conversation in ethereum/pm#711
Epoch 56832 / Slot 1818624 is both a sync committee and historical roots boundary. ETA: 2/28/2023, 4:04:48 AM UTC