0x3d1f643c3d1f…3d1f6439

ConfirmedInfrastructure573 vB78 sat/vB3 min decode

Zcash Wallet Zodl Routes Requests Through OHTTP Relays to Hide User IPs

Zcash wallet Zodl began routing requests through Cloudflare and Fastly OHTTP relays on Nov. 9, hiding user IPs from its own servers. Users need version 3.20.0.

Zodl Begins OHTTP Rollout to Shield Zcash Wallet Users’ IP Addresses
WitnessZodl Begins OHTTP Rollout to Shield Zcash Wallet Users’ IP AddressesLoboStudioHamburg / pixabay

Outputs

  1. Zodl began its OHTTP rollout on Nov. 9, reaching Android and iOS gradually over the following week.

  2. Cloudflare or Fastly relays see the user's IP address but cannot read the encrypted wallet request.

  3. The update requires Zodl version 3.20.0; F-Droid and GitHub releases were expected later that week.

  4. Zodl previously relied on community-operated lightwallet servers.

  5. The system uses the IETF's Oblivious HTTP (OHTTP) standard.

Zodl, a Zcash (ZEC) wallet, began a rollout on Nov. 9 of network infrastructure that strips users' IP addresses from the requests its own servers process. The design relies on the IETF's Oblivious HTTP (OHTTP) standard, splitting knowledge of who is asking from what is being asked. The rollout reaches Android and iOS gradually over the week following that date, with F-Droid and GitHub releases expected later in the same week, and requires version 3.20.0.

The mechanics matter here, because the privacy claim rests entirely on a separation of duties. Under OHTTP, a user's wallet request is encrypted end-to-end and sent through a relay operated by Cloudflare or Fastly. The relay can see the user's IP address but cannot decrypt the payload. Zodl's servers can decrypt and process the request but never receive the originating IP. Neither party, in theory, holds both halves of the identity puzzle.

What changes for Zodl users?

Until now, Zodl depended on community-operated lightwallet servers. That model placed trust in volunteer infrastructure whose operational standards and logging practices Zodl did not control. Moving to relay-routed OHTTP shifts the trust boundary to two large commercial CDN providers, Cloudflare and Fastly, and to the correctness of the IETF standard's implementation.

The upgrade is voluntary only in the sense that older builds keep working. Users must update to version 3.20.0 to receive the new routing path. In plain words: the wallet is outsourcing the job of hiding your address to companies whose core business is traffic routing, not privacy.

What is not said?

Zodl has not stated, in the material released so far, how the relays were selected or what contractual limits apply to Cloudflare and Fastly metadata retention. A relay that cannot read a request can still record timing, frequency and volume — patterns that, in aggregate, can narrow a user's identity even without decrypted content. The company has also not published an independent audit of the OHTTP implementation, nor a timeline for one. Every privacy architecture deserves that question, and this one is no exception.

The gradual rollout carries its own operational risk. A staged deployment across Android, iOS, F-Droid and GitHub channels means users on different versions will run different network paths for days. Whether Zodl publishes telemetry on relay failures or fallback behavior during this window remains an open question.

For the Zcash ecosystem, the move is a modest but concrete step in a longer privacy argument. Shielded transactions protect amounts and counterparties on-chain; they do nothing for the network layer, where an IP address can deanonymize a wallet user before any transaction is broadcast. Routing through oblivious relays addresses that gap — provided the relays themselves behave.

Why it matters

The pattern is not unique to Zcash. OHTTP is an IETF standard designed for exactly this class of problem, and its adoption by a consumer wallet signals a shift from protocol-level privacy toward infrastructure-level privacy, where the operator of the pipe matters as much as the cryptography inside it.

The near-term milestone to watch is the completion of the staged rollout: F-Droid and GitHub builds are due by the end of the week following Nov. 9, at which point version 3.20.0 becomes the reference implementation. Until independent parties verify the relay configuration, the privacy guarantee rests on Zodl's word and two CDN providers' infrastructure.

via tokenpost.com (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,203 articles