Propagate signature verification and peer kinds to behaviour #46
Conversation
This file contains 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
…sub-v1.1 # Conflicts: # protocols/gossipsub/src/behaviour.rs # protocols/gossipsub/src/lib.rs
AgeManning
force-pushed
the
1.1-peer-ident
branch
from
78ace4a
to
53d0ed2
Compare
… API + use it for deliveries tracking in scoring module
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've made a new type that gets injected into the behaviour.
This allows the behaviour to determine the kind of peer and if a message didn't pass validation (i.e invalid signatures) that we can use for scoring.