It does not make sense for a block to be fully-valid and assumed-valid at the same time.
Check it in CheckBlockIndex() and fix the tests that violate this assumption.
It does not make sense for a block to be fully-valid and assumed-valid at the same time.
Check it in CheckBlockIndex() and fix the tests that violate this assumption.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | fjahr, ryanofsky |
| Concept ACK | delta1, epiccurious |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
Concept ACK fa027e08f7be63c201f42d0e06160d2273b4a6dd
Concept ACK fa027e08f7be63c201f42d0e06160d2273b4a6dd.
Seems reasonable, code review ACK fa027e08f7be63c201f42d0e06160d2273b4a6dd
Not sure why this is marked as a "doc" change though.
Code review ACK fa027e08f7be63c201f42d0e06160d2273b4a6dd. This change makes sense and is an improvement over the status quo. I think it could be considered it a "doc" change since it is just adding an assert, which is a form of documentation, and not changing actual code. Not sure if that is how "doc" has been used other places, though.
This PR is a little redundant with #29370, which drops the BLOCK_ASSUMED_VALID flag entirely, so there is no way it could conflict with BLOCK_VALID_SCRIPTS. But it makes sense to check for conflicting flags as long as both flags exist.
This PR is a little redundant with #29370, which drops the BLOCK_ASSUMED_VALID flag entirely, so there is no way it could conflict with BLOCK_VALID_SCRIPTS. But it makes sense to check for conflicting flags as long as both flags exist.
Yeah, makes sense. I forgot to close this pull when the other was opened.