feat: ban a peer if its last state isn't changed after timeout #170
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
If a peer sent the same state to light client again and again, light client should ban it.
Just let the light client don't update the update timestamp for cached last-state if it isn't changed, and ban the peer when do timeout checks.
ckb-light-client/src/protocols/light_client/mod.rs
Lines 502 to 507 in 86865db
ckb-light-client/src/protocols/mod.rs
Lines 25 to 26 in 86865db
Commits: