feat: introducing node gossip type #811
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
Codecov Report
@@ Coverage Diff @@
## main #811 +/- ##
==========================================
- Coverage 83.01% 82.83% -0.19%
==========================================
Files 173 172 -1
Lines 8319 8348 +29
==========================================
+ Hits 6906 6915 +9
- Misses 1093 1111 +18
- Partials 320 322 +2 |
themantre
approved these changes
Nov 12, 2023
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.
Description
The main objective of this PR is to introduce a new node type: Node Gossip.
Node Gossip helps the P2P network by gossiping and broadcasting gossip messages.
By default, the nodes in the network are not Node Gossip, but non-gossip nodes try to protect their connections with gossip nodes.
This PR should potentially reduce network usage and help improve networking performance.
There are some other changes to improve the syncing process, unfortunately coupled with this PR.