The Privacy Blindspot of Web3 Wallets
Many cryptocurrency users believe that holding assets in a self-custodial wallet like MetaMask, Rabby, or Phantom ensures complete anonymity. While your wallet public address does not contain your name, your network broadcast metadata tells a completely different story.
Whenever your wallet checks an ERC-20 token balance, retrieves NFT metadata, or broadcasts a transaction to the mempool, it must communicate with a Remote Procedure Call (RPC) Node.
How Default RPC Providers (Infura / Alchemy) Log Your IP
By default, MetaMask routes all Ethereum Mainnet requests through Infura (operated by ConsenSys). During every single wallet query, the RPC server automatically captures:
- Your Residential Public IP Address: Disclosing your physical city, region, and Internet Service Provider.
- Your Public Ethereum Wallet Address (0x...): Creating a permanent correlation between your on-chain crypto wealth and your real-world physical location.
- Timestamped Transaction Requests: Recording precisely when and where you initiated decentralized finance (DeFi) swaps.
For more on how blockchain forensics firms correlate network telemetry with wallet identities, read our investigation on cryptocurrency IP address tracking forensics.
How to Switch to Privacy-Focused RPC Endpoints
You can instantly eliminate central RPC IP logging by configuring private, zero-logging RPC providers in MetaMask:
- Open MetaMask → Click the Network Selector dropdown → Select Add Network → Add a network manually.
- Enter a zero-knowledge RPC endpoint such as Flashbots Protect (
https://rpc.flashbots.net) or LlamaNodes Privacy RPC. - Save the custom network. Your future transactions are routed directly through MEV-protected private mempools that do not log client IP addresses.
Inspect your active IP address and verify that your browser does not leak WebRTC metadata using our free Web3 network inspector.