Modify Merge Gossip Block Validation Conditions #2621
Merged
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.
This PR addresses the first validation condition as it is currently written:
is_merge_complete(state)
-- then validate the following:execution_payload != ExecutionPayload()
As mentioned by @paulhauner in #2618, this condition might cause problems when there are forks in the POW chain at the transition boundary, potentially causing clients to initially reject and fail to propagate blocks that might be ultimately destined to become a part of the canonical chain.
It seems likely that this condition was originally intended to apply to all descendants of the transition block. Therefore it should be validated against the
BeaconState
associated with the block being imported rather than the head state. If that is true, the validation conditions simplify to this.