use correct schema definitions when creation full beacon block #8806
Conversation
This file contains 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
mehdi-aouadi
added a commit
that referenced
this pull request
Nov 4, 2024
* Decouple block and blobs publishing\import (#8728) * use correct schema definitions when creation full beacon block (#8806) * use correct schema definitions when creation full beacon block * use forkChoiceUpdatedV4 with PayloadAttributesV4 (#8752) (#8799) --------- Co-authored-by: Enrico Del Fante <enrico.delfante@consensys.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Description
Update the
DataStructureUtilto use the correct schema definitions when generating attestations for full beacon blocks.This is required in #8800 in order to make the
DataStructureUtiluse the correct schema definition when generatingAttesterSlashings andAttestations related data when dealing with fork aware spec in the tests.Fixed Issue(s)
Documentation
doc-change-requiredlabel to this PR if updates are required.Changelog