IdeaWell

Project ideas from Hacker News discussions.

Mullvad exit IPs are surprisingly identifying

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

4 Dominant Themes in the Discussion

Theme Key Take‑away Supporting Quote
1. Deterministic exit‑IP mapping The exit node is chosen deterministically from the WireGuard key, mainly to simplify load‑balancing and to prevent a single abusive user from blocking many others. “It seems more likely this is just about load‑balancing use against their available nodes.” – stevekemp
2. Trust & the “snake‑oil” debate Opinions are split: some view VPNs as genuine privacy tools, others see them as hype‑driven snake oil. “VPNs are not snake oil.” – cider9986
“VPNs are snake oil.” – wg0
3. Stable IPs enable fingerprinting & correlation A fixed exit IP lets observers link activity across services or identify a user’s multiple accounts (e.g., moderators spotting sock‑puppets). “I think you are misreading his comment… gives you a >99% chance that they are the same person.” – charcircuit
4. Real‑world utility vs. privacy promises Many users adopt VPNs for streaming, torrenting, or bypassing geo‑blocks, but they remain skeptical about any true anonymity guarantee. “I would definitely blame a VPN provider if… only a minority of users care about privacy.” – illiac786

All quotations are taken verbatim from the Hacker News thread, with the author handle cited directly.

🚀 Project Ideas

Generating project ideas…

Mullvad Exit IP Randomizer

Summary

  • Adds per-session randomization to Mullvad's deterministic exit IP assignment, preserving user‑key stability while preventing static IP fingerprinting.
  • Enables users to retain a preferred exit IP when needed, but otherwise rotate it automatically.

Details

Key Value
Target Audience Privacy‑focused WireGuard users of Mullvad and similar VPNs
Core Feature Randomizes exit IP mapping using a deterministic seed derived from the WireGuard public key plus a short‑lived nonce
Tech Stack Rust (user‑space daemon), WireGuard kernel module API, PostgreSQL for optional rotation logs
Difficulty Medium
Monetization Revenue-ready: Subscription $2.50 /month

Notes

  • Directly addresses HN complaints about privacy costs of deterministic IPs; many users would adopt it to avoid fingerprinting.
  • Provides a practical, low‑friction way to break the static mapping without abandoning Mullvad’s infrastructure.

Exit IP Transparency Dashboard

Summary

  • A web service that reveals, in real time, which Mullvad exit IP a given WireGuard key resolves to, and lets users request a new IP on demand.
  • Offers visibility into IP usage patterns, helping moderators and researchers detect abuse without invasive logging.

Details

Key Value
Target Audience Forum moderators, security researchers, developers integrating Mullvad into applications
Core Feature Real‑time query API that returns current exit IP and a simple rotate‑request endpoint
Tech Stack Node.js (Express), GraphQL, PostgreSQL, Docker
Difficulty Low
Monetization Hobby

Notes

  • HN users have asked “why not randomise it simply?” – this gives them a built‑in mechanism.
  • Utility extends to any service that needs to test or avoid blocking by known exit IP ranges.

VPN Exit IP Token Marketplace

Summary

  • A decentralized marketplace where users can lease unused Mullvad exit IP capacity as tradable tokens, enabling dynamic IP sourcing for services that block static VPN ranges.
  • Solves the blocking problem for scrapers, marketers, and geo‑testers who need a fresh, non‑blacklisted IP each request.

Details

Key Value
Target Audience Web scrapers, price‑monitoring bots, geo‑testing tools, anti‑fraud platforms
Core Feature Smart‑contract based token system that mints and burns “ExitIP” tokens representing a slice of Mullvad bandwidth
Tech Stack Solidity (Ethereum testnet), IPFS for storage, React front‑end
Difficulty High
Monetization Revenue-ready: Pay‑per‑token $0.004 per token (≈ $4 per 1 GB)

Notes

  • Directly addresses the “bans on exit ranges” frustration; token owners can rotate IPs instantly.
  • Generates discussion on balancing privacy with market‑based IP allocation, fitting HN’s tech‑economics interest.

No‑Log Exit‑IP Abuse Blocker

Summary

  • A shared reputation service that automatically flags and temporarily blocks exit IPs showing abusive patterns (e.g., repeated bans), while preserving Mullvad’s no‑log promise.
  • Reduces false‑positive blocks for legitimate users and helps moderators enforce policies without revealing user identities.

Details

Key Value
Target Audience Forum operators, CDN security teams, VPN providers looking to improve abuse handling
Core Feature Distributed CSV/JSON feed of “abuse‑flagged” IPs updated every 5 minutes, with optional per‑IP timeout
Tech Stack Go micro‑services, Redis for rate limiting, Cloudflare Workers for edge distribution
Difficulty Medium
Monetization Revenue-ready: Tiered pricing – $10/month for up to 100k IPs, $0.0001 per additional IP

Notes

  • HN thread highlighted that rotating IPs doesn’t solve underlying block‑list issues; this service provides a communal solution.
  • Could be adopted by Mullvad or similar VPNs, offering a clear value proposition for maintaining service quality.

Read Later