{"id":"XE-18153","kind":"bounty","visibility":"public","source":"web","source_repo":"","source_ref":"","source_url":"","reporter_id":613,"title":"[Re-report] XE-0025 still unfixed at HEAD 89a542e: message rate limit still keyed per libp2p peer ID - one IP runs 8 full-rate hosts","area":"node-api","claimed_tier":"high","assessed_tier":null,"verdict":null,"duplicate_of":null,"tracked":false,"internal_ref":"","internal_url":null,"status":"new","closed_reason":null,"github_state":"","disclosed_at":null,"award_xe":null,"award_approved":false,"paid_ref":"","created_at":"2026-11-18T06:45:08.678903+00:00","updated_at":"2026-11-18T06:45:08.678903+00:00","source_created_at":null,"told_at":null,"status_changed_at":null,"url":"https://bounty.xe.network/XE-18153","body":"# [Re-report] XE-0025 still unfixed at HEAD 89a542e: message rate limit is still keyed per libp2p peer ID — one IP can run 8 full-rate hosts\n\nRe-report of XE-0025 (accepted, unfixed), verified against current HEAD 89a542e.\n\n## Code evidence (current HEAD)\n\n- `net/ratelimit.go`: `allowPeer(p peer.ID)` keys buckets by **peer ID** (`l.buckets[p] = b`), with FIFO `evictOldestLocked` in `net/banstore.go:129`.\n- `net/host.go:31-39` (`NewHost`): connection gate is only a per-IP **connection-count** cap (`maxConnsPerIP`, default 8) — it does not aggregate rate-limit budget.\n- No per-IP rate accounting exists in the message path.\n\n## Impact\n\nOne IPv4 address can hold 8 simultaneous connections with distinct peer IDs. Each connection receives its **own full-rate message bucket**, so a single host gets 8× the intended message budget. FIFO eviction can additionally reset bucket histories. This multiplies DoS amplification from a single host by 8× while appearing rate-limited.\n\n## Reproduction (code-level)\n\n1. From one IP, open 8 libp2p connections to the node (distinct generated peer IDs, under `maxConnsPerIP = 8`).\n2. Send messages at the per-peer limit through each connection.\n3. All 8 pass independently — aggregate 8× budget with no 429-style rejection.\n\n## Suggested fix\n\nKey message rate buckets by `RemoteAddr` (IP), or divide the per-IP budget across that IP's connections, and move per-peer buckets to the ban store's IP-level accounting.\n\nReferenced original: XE-0025. Verified at HEAD 89a542e (`net/ratelimit.go`, `net/host.go`, `net/banstore.go`).","patch_refs":[],"thread":[]}