-
Notifications
You must be signed in to change notification settings - Fork 175
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
[Dynamic Protocol State] Refactor bootstrapping and update Benchnet2 automations #5136
[Dynamic Protocol State] Refactor bootstrapping and update Benchnet2 automations #5136
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## feature/dynamic-protocol-state #5136 +/- ##
==================================================================
+ Coverage 56.48% 56.53% +0.04%
==================================================================
Files 987 987
Lines 92531 92533 +2
==================================================================
+ Hits 52270 52315 +45
+ Misses 36414 36378 -36
+ Partials 3847 3840 -7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…tocol-state-bn-testing
we use the time between rootblock and finalize on Mainnet to create state commitment, speeding up spork time. Hence maintaining that structure here
commit passes bootstrapping tests, and builds on bn2
…tocol-state-bn-testing
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.
Looks good, I like how you consolidated intermediate data in a typed structure
5291963
into
feature/dynamic-protocol-state
This PR modifies the bootstrapping CLI and Benchnet2 automations to be compatible with Dynamic Protocol State changes.
Changes
rootblock
command (previously infinalize
)rootblock
.rootblock
, but required again infinalize
is consolidated into theintermediary-bootstrapping-data.json
file.cmd/bootstrap/README.md
example commands so it is again easy to manually go through the bootstrapping process using the example files committed to the repo.