-
Notifications
You must be signed in to change notification settings - Fork 746
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
Electra engine api #5743
Electra engine api #5743
Conversation
* update * experiment * superstruct changes * revert * superstruct changes * fix tests * indexed attestation * indexed attestation superstruct * updated TODOs
* `superstruct` Attester Fork Variants * Push a little further * Deal with Encode / Decode of AttesterSlashing * not so sure about this.. * Stop Encode/Decode Bounds from Propagating Out * Tons of Changes.. * More Conversions to AttestationRef * Add AsReference trait (#15) * Add AsReference trait * Fix some snafus * Got it Compiling! :D * Got Tests Building * Get beacon chain tests compiling --------- Co-authored-by: Michael Sproul <micsproul@gmail.com>
* Upgrade `superstruct` to `0.8.0` * superstruct `AggregateAndProof`
Merge unstable into Electra attestation changes
…/lighthouse into block-processing-electra
…/lighthouse into block-processing-electra
Add electra lightclient types
Avoid changing slasher schema for Electra
…ectra_attestation_changes
…bigsean/lighthouse into block-processing-electra
…ghthouse into electra-epoch-proc
… into electra-engine-api
Yes since we were planning to merge it into unstable after epoch processing, re-targeted the branch to fix the diff |
Something that's missing is the payload bodies by range changes: ethereum/execution-apis#545 This PR implements an extension of the existing V1 endpoint, what's currently spec'd is to actually add a V2 endpoint: ethereum/execution-apis#545 (comment) There may be further discussion about whether to just extend v1 but for now we won't be able to serve blocks whose payloads we've pruned until we implement this as a v2 We could use the same |
Strong agree on extending V1. We can implement the V2 method but its unnecessarily complex and gains us nothing imo. |
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.
woop!
@mergify queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 2a13b4f |
Issue Addressed
N/A
Proposed Changes
Implements electra engine api.
Additional Info
The spec does not handle the
engine_getPayloadBodies
for the new electra fields. We need to add it to the spec and implement it.This PR currently implements it in the manner that I think it will be implemented (i.e. by extending
ExecutionPayloadBodyV1
to includedeposit_receipts
andwithdrawal_requests
.Working on getting a spec out for this.