Security: Fix p2p-max-nodes-per-host and add P2P peer tools #20
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.
Summary
p2p-max-nodes-per-hostfrom100to2to prevent connection exhaustion attacks (fixes major config error on the fullnode config file #17, related to major error on the fullnode config #18)get_p2p_nodes.shto discover and test P2P peers by latencypeers.txtwith 16 verified active mainnet P2P peers (tested January 2026)Security Issue
With
p2p-max-nodes-per-host = 100andmax-clients = 100, a malicious node could occupy all incoming connections from a single host, preventing legitimate peers from connecting. This change limits connections per host to 2, which is the recommended setting.Files Changed
xprNode/config.inixprNode/get_p2p_nodes.shxprNode/peers.txtTest Plan
Related
🤖 Generated with Claude Code