decentraland / comms-gatekeeper / 26661766696

85%

main: 85%

Build Type

Pull #263

github

Committed by decentraland-bot

Commit Message

Add IP banning feature: connection logging, IP bans, and transitive banning

- New migration (1772000000000_ip-banning) adds connection_logs and ip_bans
  tables. connection_logs records wallet↔IP pairs on every successful token
  request; a 90-day TTL cleanup cron is a follow-up item.

- IP extraction (x-forwarded-for → x-real-ip) runs on every comms-scene
  request; the (address, ip) pair is logged after credentials are issued.

- IP ban check is performed before issuing a token; banned IPs receive 403.

- New DB adapter (ip-moderation-db) and logic component (ip-moderation)
  mirror the existing user-moderation layer: banIp, liftIpBan,
  getIpBanStatus, logConnection, getIpsByAddress, getAddressesByIp,
  banAllIpsForAddress, banAllAddressesForIp.

- New REST endpoints: POST/GET/DELETE /ips/:ip/bans, GET /users/:address/ips,
  GET /ips/:ip/users; all protected by the existing moderator middleware.

- POST /users/:address/bans gains an optional banAllKnownIps boolean for
  transitive banning; POST /ips/:ip/bans gains banAllKnownAddresses.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Pull Request Pull Request #263: Add IP banning: connection logging, IP bans, and transitive banning

Coverage Stats

1102 of 1440 branches covered (76.53%)

Branch coverage included in aggregate %.

162 of 196 new or added lines in 17 files covered. (82.65%)

2 existing lines in 1 file now uncovered.

3163 of 3590 relevant lines covered (88.11%)

73.87 hits per line