How Blockchain Wallets Can Leak Metadata (And How to Reduce It)

Table of Contents

• The Myth of Complete Anonymity
• How RPC Nodes Expose Your Metadata
• What is Oblivious HTTP (OHTTP)?
• Implementing Metadata Shielding
• Summary
• FAQ
• References
• Related Articles

The Myth of Complete Anonymity

This article explains how standard blockchain wallets expose your IP address and metadata to RPC nodes, and explores modern solutions like Oblivious HTTP (OHTTP) to protect your digital identity.

When interacting with a blockchain, many users assume that their transactions are completely anonymous because their identities are masked by cryptographic addresses. While it is true that your name is not directly attached to a wallet address, the network layer tells a very different story.

Every time you open your wallet app to check your balance or sign a transaction, your device must communicate with the blockchain. This communication often relies on third-party infrastructure, which can inadvertently leak sensitive metadata.

How RPC Nodes Expose Your Metadata

Most non-custodial wallets do not run a full blockchain node locally on your mobile device. Instead, they rely on Remote Procedure Call (RPC) nodes. These nodes act as a bridge, querying the blockchain on behalf of your wallet.

However, this architecture introduces a critical privacy flaw:

1. IP Address Exposure: When your wallet connects to an RPC node, it transmits your home or mobile IP address.
2. Behavioral Linking: RPC providers can correlate your IP address with the specific wallet addresses you are querying. Over time, this builds a behavioral profile that links your physical location to your on-chain assets.

Even if you use a VPN, the RPC provider still knows exactly which wallet addresses are being queried together at the same time.

What is Oblivious HTTP (OHTTP)?

To solve this network-level metadata leak, security researchers and engineers have turned to Oblivious HTTP (OHTTP). OHTTP is an IETF protocol under active standardization designed to separate the identity of the requester (IP address) from the content of the request.

It works by using a double-blind relay system—a network setup where the server forwarding your request cannot read its contents, and the server fulfilling your request cannot see your identity.

• The Relay: Receives your request and masks your IP address. The relay does not possess the cryptographic key required to read the contents of your request.
• The Gateway: Receives the masked request from the relay. It possesses the key to decrypt and fulfill the request, but it has no idea who sent it, because the IP address was stripped by the relay.

By separating the “who” from the “what,” OHTTP ensures that no single entity has both your identity and your data.

Implementing Metadata Shielding

Modern wallet architectures are beginning to implement these privacy-preserving standards to protect end-users by default.

As an example, according to its published specifications, the Palmo Wallet is designed to employ a metadata shielding system based on OHTTP. Instead of calling public RPCs directly, traffic is routed through a blind relay. The payload is encrypted using hybrid cryptography (for example, ECDH P-256 + Kyber-1024). The exact hybrid construction depends on the implementation. The relay forwards this encrypted payload to a decrypting gateway, ensuring that the relay only sees the IP address, while the gateway only sees the transaction data.

This separation of knowledge is how modern, institutional-grade non-custodial systems improve resistance against metadata correlation.

Summary

Blockchain wallets inherently leak metadata like IP addresses when communicating with standard RPC nodes. To truly protect your digital identity, relying on basic HTTPS is not enough. Solutions like Oblivious HTTP (OHTTP) provide a robust architectural fix by separating your network identity from your blockchain requests. When choosing a wallet, look for platforms that prioritize network-level metadata shielding.

FAQ

Q: Does a VPN protect my wallet metadata? A: A VPN hides your IP address from your ISP and changes your apparent location, but the RPC provider still sees all your wallet addresses grouped under the VPN’s IP address. They may still be able to correlate activity linking those addresses together.

Q: Why don’t all wallets use OHTTP? A: OHTTP is a relatively new standard and requires significant backend infrastructure (running separate relays and gateways) which increases operational complexity for wallet providers.

Q: Does OHTTP slow down transactions? A: There is a minor latency overhead due to the double-hop routing (Relay -> Gateway), but for typical wallet operations like broadcasting a transaction, the difference is negligible.

Q: Can a self-hosted node solve this problem? A: Yes, running your own full node locally ensures your queries never leave your trusted network. However, for mobile users, running a full node is often impractical due to storage, bandwidth, and battery constraints.

References

• RFC 9458: Oblivious HTTP
• Cloudflare: What is Oblivious HTTP?
• Understanding RPC Nodes in Web3

Learning Path

• How Blockchain Wallets Can Leak Metadata
• Designing a Secure Modular Android Wallet
• AGPL vs MIT vs Apache: Which License Fits a Crypto Wallet?
• ORCIB Developer Documentation