core: fix systemcontracts.GenesisHash when run bsc firstly without init #2132
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
buddh0
changed the title
buddh0
force-pushed
the
systemcontracts_GenesisHash
branch
from
1a12ff5 to
e94d6f4
Compare
buddh0
changed the title
weiihann
approved these changes
Jan 4, 2024
zlacfzy
approved these changes
Jan 4, 2024
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.
Description
core: fix systemcontracts.GenesisHash when run bsc firstly without init
Rationale
after #2015 and #2100
bsc mainnet and chapel can run without
geth initbut may lead a empty genesis hash when first startup, this PR is to fix it
Example
add an example CLI or API response...
Changes
Notable changes: