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

Engine API changes for Capella #6318

Closed
StefanBratanov opened this issue Oct 13, 2022 · 0 comments
Closed

Engine API changes for Capella #6318

StefanBratanov opened this issue Oct 13, 2022 · 0 comments
Assignees
@rolfyone
Labels
Epic Capella Issues required to implement Capella upgrade

Comments

@StefanBratanov
Copy link
Contributor

StefanBratanov commented Oct 13, 2022 •
edited
Loading

https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/fork-choice.md#extended-payloadattributes
@StefanBratanov StefanBratanov mentioned this issue Oct 13, 2022
Closed
10 tasks
@rolfyone rolfyone added the Epic Capella Issues required to implement Capella upgrade label Nov 1, 2022
@rolfyone rolfyone changed the title Extend PayloadAttributes for Capella Engine API changes for Capella Nov 9, 2022
@rolfyone rolfyone self-assigned this Nov 13, 2022
rolfyone added a commit to rolfyone/teku that referenced this issue Nov 14, 2022
@rolfyone
Added execution payload capella objects
ca407c5 
 - added RPC's for capella for execution engine client.

 partially addresses Consensys#6318

Signed-off-by: Paul Harris <paul.harris@consensys.net>
@rolfyone rolfyone mentioned this issue Nov 14, 2022
Merged
2 tasks
rolfyone added a commit that referenced this issue Nov 15, 2022
@rolfyone
Added execution payload capella objects (#6438)
080f5a5 
 partially addresses #6318

Signed-off-by: Paul Harris <paul.harris@consensys.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rolfyone rolfyone

Labels
Epic Capella Issues required to implement Capella upgrade
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rolfyone @StefanBratanov