As reported on November 11, 2026, Zodl was rolling out a new server architecture with its Zcash wallet version 3.20.0. Its central change is a default network-privacy measure: a relay can see a user’s IP address, while Zodl’s gateway can read the wallet request, but neither operator should see both through the ordinary request path.

Where the information is split
A mobile light wallet relies on remote infrastructure to retrieve chain data and broadcast transactions. Without an intermediary, the server handling those requests can see the user’s IP address, what was requested and when. Shielding ZEC activity on-chain does not, by itself, conceal that network metadata.
Zodl’s design uses Oblivious HTTP (OHTTP) to divide the connection:
- The wallet encrypts a request so that only Zodl’s gateway can open it.
- A relay operated by Cloudflare or Fastly receives the encrypted request. It can see the connecting IP address but not the request contents, and forwards the request without the identifying network header.
- Zodl’s gateway decrypts the request and passes it to a lightwalletd server. The gateway sees the request but receives it from the relay’s address rather than the user’s.
The source’s account of the published code describes further measures against correlation: requests are padded in roughly 4 KB increments, with transaction broadcasts padded to at least 16 KB; sensitive responses are padded too. It says relay request IDs are not stored in Zodl logs as plaintext. Instead, the gateway records HMAC-derived values using a key held only in memory and lost when the gateway restarts. These measures are intended to make traffic size and later log matching less revealing; they do not remove every observable signal.

The trust boundary remains
The separation depends on the relay operator and Zodl not cooperating to match their observations. A relay can still observe connection times and approximate traffic volume. Zcash community critics also raised concerns about reliance on Cloudflare and Fastly, both US companies subject to legal demands. Zodl contributor y4ss acknowledged the limitation, describing OHTTP as a better default rather than a replacement for Tor or Nym against a powerful state-level adversary. Users concerned about pressure on the underlying cloud infrastructure can, y4ss said, enable Zodl’s Tor option on top of OHTTP, so the relay sees a Tor exit address instead of their own IP. Zodl also allows users to switch to community nodes in advanced settings.

Other approaches reported at the time
The November 2026 report placed Zodl alongside several distinct efforts to protect network metadata:
- Nym mixnet: Nym said in September that Zcash wallets Zingo and Zkool had integrated mixnet access and that it was in talks with Zodl. Mixnets use multiple hops and cover traffic to make connections harder to correlate, at a cost in latency.
- Ethereum RPC routing: The Kohaku command-line tool routes traffic other than calls to a self-hosted local RPC through Tor by default, according to the report. The Ethereum Foundation’s anon-rpc proposal aims to give wallets an interface to anonymity networks. The report said a version supporting Tor and Nym was running on mainnet and had been adopted by the Privacy Pools v2 web interface.
- Flashnet: Described as Flashbots research into anonymous Ethereum transaction submission, it had no reported mainnet deployment or benchmark results at the time. Its proposed shared batches and secret-sharing process should not be treated as a demonstrated production safeguard.
- Bitcoin Core: The report said version 31.0 added an optional transaction-broadcast feature using Tor or I2P, with a separate connection per transaction. It also described a fallback bug disclosed in June 2026 that could expose an IP address after a failed anonymous handshake, and said version 31.1 fixed it.
These systems protect different handoffs. Zodl’s default OHTTP path limits what one service operator learns from a wallet request; it does not eliminate dependence on the relay and gateway or provide the same routing properties as Tor or a mixnet.



