chore: make post envelope beacon api spec compliant#9276
Open
shane-moore wants to merge 4 commits into
Open
Conversation
shane-moore
force-pushed
the
chore/post-envelope-spec-compliance
branch
from
032fefe to
52b5798
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Issue Addressed
Part of #8828 for the stateful path and aligns
POST /eth/v1/beacon/execution_payload_envelopewith beacon-APIs PR ethereum/beacon-APIs#580.Proposed Changes
broadcast_validationquery parameter (gossipdefault,consensus,consensus_and_equivocation)Eth-Consensus-Versionheader202when the envelope is broadcast but fails import (was500)Additional Info
415on badContent-Typenot addressed as to match the existing block POST flowbeacon_block_root