Cap on peers database size - #2449
Open
kushti wants to merge 64 commits into
Open
Conversation
Validate NiPoPoW proof parameters
Reject proofs whose header chain contains invalid Autolykos PoW before bootstrap headers are applied. Add regression coverage demonstrating that rejected proof headers are not inserted into history.
Restore the v6.0.5 node and integration-test builds under fatal unused-import warnings.
Validate NiPoPoW proof header PoW
Fix fee estimation bounds
Reject invalid inbound NiPoPoW parameters
Preserve asset issuance with token burn requests
Bound per-peer outbound buffering
…-cleanup Close all live connections for blacklisted IPs
Clarify comment regarding state after headers-only fork.
Resume deferred ExtraIndexer catch-up without reindexing
Post 6.0.4 additional tests
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
In this pull request, max cap on peer database size is introduced. Also, when the node is sending known peers list to a peer, it is doing a random slice from all the database and then working with it (shuffling and slicing a smaller set), instead of doing costly shuffling with all the database