feat: basic PeerBook implementation. #34
Merged
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
This behaviour also utilizes connection limits, based on a behaviour in libp2p PR, which will also allow peers to bypass the limits if they are whitelisted.
Note: This does not provide any form of persistence so any future peers will need to be manually added
TODO: Expand on test
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.
This behaviour will handle storing peer identify info, rtt, as well as a whitelist for the connection limits implementation, which would allow a peer who is whitelisted to bypass such limits and be able to establish a connection.
This implementation will also begin to split apart
SwarmAPIto eventually begin the process of deprecating or refactoring it in the future.