forked from ethereum/beacon-APIs
-
Notifications
You must be signed in to change notification settings - Fork 0
add flag to include payload in produceBlockV4 #2
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
Open
shane-moore
wants to merge
2
commits into
epbs-standardized
Choose a base branch
from
produce-block-v4-with-payload
base: epbs-standardized
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+71
−3
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| Gloas: | ||
| BlockContents: | ||
| type: object | ||
| description: | | ||
| Block contents for self-building, including the execution payload envelope | ||
| and blobs. This enables stateless failover to another beacon node for publishing, | ||
| as all required data is returned in a single response. | ||
| required: [block, execution_payload_envelope, kzg_proofs, blobs] | ||
| properties: | ||
| block: | ||
| $ref: "./block.yaml#/Gloas/BeaconBlock" | ||
| execution_payload_envelope: | ||
| $ref: "./execution_payload_envelope.yaml#/Gloas/ExecutionPayloadEnvelope" | ||
| kzg_proofs: | ||
| $ref: "../fulu/block_contents.yaml#/Fulu/KZGProofs" | ||
| blobs: | ||
| $ref: "../deneb/block_contents.yaml#/Deneb/Blobs" |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
in ethereum#519 the conclusion was to leave it up to clients to support blinding the response, eg. in Lodestar we have a flag
--blindedLocaland corresponding query param to tell the bn to not return full block contents but rather cache them which makes the block production stateful but there is no drawback in a 1:1 setupI think it would be good to standardize this kind of query parameter in
produceBlockV4and leave it up to clients whether the wanna implement it or not, ie. if a client doesn't wanna implement it they can always set the query param tofalse