-
Notifications
You must be signed in to change notification settings - Fork 677
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
feat: add config parameters for burn block start #4556
Conversation
dc2c59e
to
d8bf9e7
Compare
d8bf9e7
to
420f132
Compare
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.
LGTM!
a50817d
to
44ad74a
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## next #4556 +/- ##
===========================================
- Coverage 84.37% 66.75% -17.62%
===========================================
Files 471 471
Lines 337762 337942 +180
Branches 317 317
===========================================
- Hits 284973 225609 -59364
- Misses 52781 112325 +59544
Partials 8 8
... and 272 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Epoch 1.0 must be before the start block and epoch 2.0 must be equal to the start block.
These failing tests were fixed in #4578. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
Added configuration parameters to customize the burn block at which to start processing Stacks blocks, when running on testnet or regtest.
Applicable issues
Additional info (benefits, drawbacks, caveats)
Checklist
docs/rpc/openapi.yaml
andrpc-endpoints.md
for v2 endpoints,event-dispatcher.md
for new events)clarity-benchmarking
repobitcoin-tests.yml