-
-
Notifications
You must be signed in to change notification settings - Fork 346
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Bump to new gossipsub * Fix test type errors * Add getMeshPeers method * Cleanup test nodes on success and error * Add allowPublishToZeroPeers option * Add allowPublishToZeroPeers to dev options * Add scripts to run dev servers * Bump gossipsub * Bump gossipsub * Expose gossip peer score stats * bump gossipsub * Dump gossipsub score params * Bump lodestar * Add behaviourPenaltyThreshold to gossip scoring params * Switch to latest gossipsub update * Fix cli unit test * Fix unknownBlockSync e2e test * Update latest gossipsub * Fix e2e - network addr in use * Use latest gossipsub 3efae56c9d39ff3a047a7e6c65fa32e5756bebde * Use latest gossipsub 039af54c7bf47396c1be414d9fa33aa2e8cc2697 * Increase meshMessageDeliveriesWindow and gossipsubIWantFollowupMs * Set gossipsubIWantFollowupMs and meshMessageDeliveriesWindow 12s * Reset gossipsub metric behaviourPenalty per scrape * Compute score using lodestar score and gossipsub score (#3875) * Refactor PeerRpcScoreStore: add PeerScore class * Aggregate lodestarScore, gossipsubScore to compute final score * updateGossipsubScores util and unit test * Populate PeerScore on updateGossipsubScore * Fix peerManager e2e test * Fix test/sim/multiNodeSingleThread.test.ts * Update latest gossipsub * lodestar_gossip_mesh_peers_by_client_count metric * Log sent peers in gossipsub.publishObject() * Fix lodestar_gossip_mesh_peers_by_client_count metric * Fix lodestar_gossip_mesh_peers_by_client_count metric * Add asyncValidation=true option to gossipsub * Fix sha256 usage * Go with libp2p-gossipsub 0.14.0 Co-authored-by: Tuyen Nguyen <[email protected]> Co-authored-by: Cayman <[email protected]>
- Loading branch information
1 parent
111b194
commit d61d898
Showing
35 changed files
with
643 additions
and
584 deletions.
There are no files selected for viewing
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 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 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 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 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 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 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 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
Oops, something went wrong.