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.

Sign up for GitHub

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

Jump to bottom

Add support for capella blocks #1464

Closed
dB2510 opened this issue Nov 20, 2022 · 4 comments
Closed

Add support for capella blocks #1464

dB2510 opened this issue Nov 20, 2022 · 4 comments
Assignees
@xenowits

Comments

@dB2510
Copy link
Contributor

dB2510 commented Nov 20, 2022 •
edited
Loading

Problem to be solved

Ethereum is eyeing to introduce withdrawals in next upgrade (shanghai). This introduces new block version named capella which introduces some new fields to BeaconBlockBody and ExecutionPayload. For more details refer.

Proposed solution

  • Add support for capella versioned beacon block wherever block version is considered across charon codebase.
  • Add relevant tests.
@corverroos
Copy link
Contributor

What is the timeline on this for goerli and gnosis? ie, by when does need to be in?

@dB2510
Copy link
Contributor Author

dB2510 commented Nov 21, 2022

What is the timeline on this for goerli and gnosis? ie, by when does need to be in?

There is no announcement for specific date as when it will be live on goerli or gnosis, but client teams are under development currently. go-eth2-client has already added support.
We can track shanghai upgrade planning here: ethereum/pm#450.

@dB2510
Copy link
Contributor Author

dB2510 commented Nov 21, 2022

Issues from client teams:

@thomasheremans
Copy link
Contributor

Target: Early Jan

@xenowits xenowits mentioned this issue Dec 16, 2022
Merged
obol-bulldozer bot pushed a commit that referenced this issue Jan 4, 2023
@xenowits
core: add support for capella blocks (#1570)
23f981f 
Adds support for capella blocks.

category: feature
ticket: #1464
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xenowits xenowits

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@corverroos @dB2510 @xenowits @thomasheremans