Beacon Node Syncing, Network Infrastructure and Core Services #286
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
- Add network crate. - Add sync crate. - Add version crate. - Add lighthouse configuration. - Add network configuration.
- Basic network message handler threading - Correct references
- Implements ClientTypes - New network BeaconChain type for the networking service
AgeManning
added
ready-for-review
AgeManning
changed the title
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.
Issue Addressed
This PR addresses #248. It constructs the basic
beacon_nodeservice structure, notifier service and networking services (specifically the implementation of libp2p gossipsub).The initial networking stack will consist of tcp, dns, multiplexing with mplex or yamux, encryption with secio (with ed25519 keypairs) and gossipsub as the routing mechanism.
Note: These parameters will need to be modified to fit with the wire protocol currently being discussed here: ethereum/consensus-specs#692
The networking messaging is designed to fit as close to the Wire 0 protocol as possible.