-
Notifications
You must be signed in to change notification settings - Fork 20.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/utils: if dev-mode is enabled and db is pre-existing, validate that genesis configuration is compatible #28468
Merged
fjl
merged 6 commits into
ethereum:master
from
jwasinger:validate-preexisting-devmode-genesis
Nov 22, 2023
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
ca2e977
validate development mode genesis configuration
jwasinger 057468b
appease linter
jwasinger 9f29f42
simplify
jwasinger e057ddd
address nitpick
jwasinger 59bdc00
make developer genesis block difficulty 1. add additional checks for…
jwasinger 437471b
cmd/utils: update error messages
fjl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This check is not enough. The setting TerminalTotalDifficultyPassed configures some aspects of the client to assume the merge has happened, but the actual trigger for the merge is whether the total difficulty is higher than TTD. So you need to add a check here that expects
TerminalTotalDifficulty
to be set, andDifficulty
of the genesis block to be higher thanTerminalTotalDifficulty
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's interesting is that the default dev mode configuration sets the total difficulty to 0, ttd to 0, and terminalTotalDifficultyPassed to true (so the conf is invalid and/or the merge should happen on block 1). But the simulated beacon initially sets the genesis as the finalized block and we accept it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just a weird edge-case that we don't validate in
forkchoiceUpdated
because it would never have occured on mainnet. we just blindly accept going firmly into proof-of-stake if the beacon client indicates a finalized block.