Engine API: replace INVALID_TERMINAL_BLOCK with INVALID + lvh=0x00..00 #217
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.
Implements Option 3 from #212, that is:
INVALID_TERMINAL_BLOCK
status with{status: INVALID, latestValidHash=0x00..00}
which simplifies the spec and CL implementationsINVALID
by returning{status: INVALID, latestValidHash=0x00..00}
A list of places where according to this change EL must respond
{status: INVALID, latestValidHash=0x00..00}
:INVALID_TERMINAL_BLOCK
headBlockHash
infcU
callThis proposal does not break existing testnets which have already transitioned to PoS e.g. Kiln.
Note:
INVALID_TERMINAL_BLOCK
status should be removed from Optimistic Sync spec if this PR is merged.