Eth-Consensus-version header now passed for json block production from VC #8754
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.
When producing a block, JSON payloads require the Eth-Consensus-version header.
Generally using SSZ this was correct, but there was no test case for JSON block production, and it wasn't providing the header correctly.
Because probably 99% of our block production is via SSZ, this was not really visible.
This would not be a problem for local BN+VC, but if the teku VC ever falls back to json (or is instructed to produce JSON), block production could potentially fail if the BN is following spec.
Changed an AT to check both SSZ and JSON block production.
fixes #8753
Documentation
doc-change-required
label to this PR if updates are required.Changelog