fix: don't sync block filter hashes if finalized checkpoint is too less than the last proved header #169
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.
Why
< self.check_point_interval * 2
?ckb-light-client/src/protocols/light_client/peers.rs
Lines 539 to 541 in fc45e35
Because light client don't finalize the latest checkpoint, light client will keep a checkpoint as a safe distance, so it doesn't have to rollback such many blocks even there is a fork. (N.B. Light client won't handle a long fork.)
check_point_interval
asSo, as an approximated value, I use
< self.check_point_interval * 2
here.Ref: the 2nd issue in #168 (comment).