Zodl Deploys OHTTP to Sever the Link Between IP Addresses and Wallet Activity
TREE NEWS reports: Zcash wallet Zodl has begun operating its own wallet servers and, in partnership with Cloudflare and Fastly, is rolling out Oblivious HTTP (OHTTP) technology. The move is designed to reduce the risk that a user’s IP address can be correlated with their wallet activity — a privacy leak that has long undermined the practical anonymity of even the most privacy-focused chains.
The problem OHTTP solves
Most wallet software routes requests through a server that inevitably sees both the client’s IP address and the content of the request. Even on a shielded chain like Zcash, where transaction contents are encrypted, that metadata can be enough to deanonymize users: an observer who links an IP to a wallet can infer balances, timing, and counterparties through traffic analysis alone.
OHTTP addresses this by splitting the request path. A relay run by a third party (here, Cloudflare or Fastly) forwards encrypted requests to Zodl’s own gateway without being able to read them, while the gateway processes the request without seeing the originating IP. Neither party holds both pieces of the puzzle, which sharply reduces the value of any single point of surveillance.
Why it matters for the privacy-coin narrative
- Metadata is the last frontier: As shielded transaction technology matures, network-level leaks become the primary attack surface for privacy users.
- Mainstream infrastructure: Partnering with Cloudflare and Fastly signals that privacy tooling is moving onto commodity CDN infrastructure rather than bespoke anonymity networks.
- Self-operated servers: By running its own backend, Zodl avoids depending on third-party node providers that could log or be compelled to hand over user data.
Industry implications
The deployment reflects a broader shift in the wallet sector, where providers are increasingly competing on privacy guarantees rather than feature checklists. For Zcash specifically, it strengthens the case that shielded transactions are only as private as the network layer surrounding them. It also puts pressure on rival privacy wallets to match the standard, and could set a template for how OHTTP is adopted across the crypto stack — from light clients to RPC providers.
Regulatory scrutiny is the obvious counterweight. Privacy-enhancing tools have drawn attention from policymakers who worry about illicit finance, and any wallet that advertises stronger anonymity will face questions about compliance. Zodl’s architecture, which keeps servers in-house and relies on neutral relays, may offer a defensible middle ground.
Looking ahead
Expect OHTTP to become a baseline expectation for privacy-oriented wallets within the next year, and watch whether other chains adopt similar relay-plus-gateway designs. The real test will be adoption: if users enable the feature by default, the privacy gain is meaningful; if it remains an opt-in toggle, the metadata leak persists for most of the user base.
