-
Notifications
You must be signed in to change notification settings - Fork 459
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
Add holesky configs and chainspec #6034
Conversation
"LogFileName": "holesky.logs.txt" | ||
}, | ||
"Sync": { | ||
"FastSync": true |
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.
+SnapSync true?
I guess we have to add pivot, probably genesis block in this case. I haven't checked how pivots work with genesis though.
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.
Please check here
#6034 (comment)
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.
Okay, please make sure any network can work without pivots. I am not so sure about it. It would be nice to know not only in holesky context
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.
Consider adding Can_load_holesky tests, check also BlockchainIds class
* Add holesky configs and chainspec * fixes * Add tests and fix for 4788 address * adjust shanghai timestamp for holeskey to be genesis + (256*12)
Resolves #6032
Changes
Types of changes
What types of changes does your code introduce?
Testing
Requires testing
If yes, did you write tests?
Documentation
Requires documentation update
#6033
Requires explanation in Release Notes
Release Notes: