This repository was archived by the owner on Aug 23, 2020. It is now read-only.
Feat: Making IRI use the initialSnapshot and the solidEntryPoints #1135
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.
Description
This PR contains the changes that are necessary for checking against the solidEntryPoints instead of the NULL_HASH. It does not activate the creation of local snapshots, yet and also doesn't modify the LedgerValidator and MIlestoneTracker to change the "latestSnapshot" instance. The "initialSnapshot" that holds the solidEntryPoints is however read already from the new SnapshotProvider so this activates parts of the new code already. Since the "initialSnapshot" will be the last global snapshot (with the NULL_HASH as its only solidEntryPoint) in the absence of local snapshot files, it is a non-breaking change.
Once this PR is merged there will be a last PR that also enables the use of the "latestSnapshot" instance, which will fully enable the new features.
Type of change
How Has This Been Tested?
Checklist:
Please delete items that are not relevant.