Separate FIRST_BLOCK and TRACE_FIRST_BLOCK option for blocks import and tracing methods #5014
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.
Motivation
Currently, we have
FIRST_BLOCK
andLAST_BLOCK
to manage the range of blocks to index. But, for instance, the archive node can be partially archive node: there is no archive state until a specific block number. In that setup, Blockscout will not import any block less thanFIRST_BLOCK
, if it is set up. The idea is to add more flexibility and to separate block import and tracing methods to be available to import blocks from partial archive node even without internal transactions.Changelog
TRACE_FIRST_BLOCK
andTRACE_LAST_BLOCK
are addedChecklist for your Pull Request (PR)
CHANGELOG.md
with this PRmaster
in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.