Draft
Conversation
when the `verify` launch option is set: 1. the node will launch from local state without joining the network 2. it will then iterate through all storage_modules validating different indices and proofs 3. any chunk that fails validation will be flagged as invalid 4. the next time the node is launchd with syncing enabled it will try to sync and pack the flagged chunks This change also refactors the code for validating proofs. It introduces a #chunk_proof record which could eventually replace the tuples and maps that are currently used when dealing with proofs. This is just an initial step, though, and the chunk_proof record is only used internally (i.e. no updates to any serialized data structures)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.