Skip to content

Conversation

@paulgnz
Copy link
Collaborator

@paulgnz paulgnz commented Jan 22, 2026

Summary

Security Issue

With p2p-max-nodes-per-host = 100 and max-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

File Change
xprNode/config.ini Security fix for p2p-max-nodes-per-host
xprNode/get_p2p_nodes.sh New script to discover/test P2P peers
xprNode/peers.txt Verified active mainnet P2P peers

Test Plan

Related

🤖 Generated with Claude Code

- Change p2p-max-nodes-per-host from 100 to 2 to prevent connection
  exhaustion attacks (fixes XPRNetwork#17)
- Add get_p2p_nodes.sh script to discover and test P2P peers by latency
- Add peers.txt with 16 verified active mainnet P2P peers (Jan 2026)

This addresses the security vulnerability where a malicious node could
occupy all incoming connections by setting p2p-max-nodes-per-host too high.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

major config error on the fullnode config file

1 participant