A shielded transaction can hide activity on-chain without hiding the network connection used to check a wallet or broadcast a transaction. As reported on November 11, 2026, Zcash wallet Zodl was rolling out version 3.20.0 with Oblivious HTTP (OHTTP) protection enabled by default. The comparison question is what each available approach conceals from the servers handling wallet traffic—and what it still leaves exposed.
Light wallets rely on remote servers rather than storing a complete blockchain locally. In Zcash, a wallet may request data from a lightwalletd server. A direct connection can reveal the user’s IP address, request and timing to that server, even when the ZEC activity itself is shielded on-chain. The concern extends beyond Zcash: developer b10c documented an entity called LinkingLion in 2023 that monitored which Bitcoin nodes first broadcast transactions. Its activity appeared to date back to 2018; b10c also observed IP addresses from the same ranges connecting to Monero nodes.

What Zodl changes
Zodl’s new route separates a request between an OHTTP relay, operated by Cloudflare or Fastly, and a ZODL gateway. The wallet encrypts the request for the gateway before sending it to the relay. The relay can see the connecting IP address but cannot read the request; the gateway can decrypt the request but sees the relay’s address rather than the wallet’s. The gateway then passes the request to lightwalletd.
The reported implementation also pads outgoing requests to size increments of about 4 KB, with transaction broadcasts padded to at least 16 KB; sensitive responses are padded too. According to the source’s account of the published code, relay request IDs are not stored in plaintext in ZODL logs. Instead, the gateway logs HMAC fingerprints calculated with a key held only in memory and destroyed on restart. These measures are intended to make traffic-size analysis and later log matching harder—not to make them impossible under every threat model.

At the reporting date, the code had just launched and Zodl said it would roll the upgrade out to all users over the following days. Unlike Zodl’s earlier optional Tor setting, OHTTP protection was designed to require no manual setup.

Different routes, different limits
- OHTTP: Separates the wallet’s IP address from its request content across two operators, provided the relay and gateway do not collude. The relay still sees connection timing and approximate traffic volume. Zcash community critics warned that reliance on Cloudflare and Fastly, both US companies subject to legal demands, could create a false sense of security. ZODL contributor y4ss acknowledged that OHTTP is a better default, not a substitute for Tor or Nym against a state-level adversary. Zodl users can also enable Tor on top, so the relay sees a Tor exit address instead of their own.
- Mixnets: Nym’s approach uses multiple relays, uniform packet sizes and decoy traffic to make incoming and outgoing traffic harder to match, at the cost of added latency. Nym said in September 2026 that Zcash wallets Zingo and Zkool had integrated its mixnet in different ways and that it was discussing cooperation with Zodl. It announced an integration SDK at Devcon 8 in the week before the report.
- Tor-based wallet and broadcast routes: The Ethereum Foundation’s Kohaku command-line tool sends traffic other than local, self-hosted RPC calls through Tor by default. Its separate anon-rpc proposal, introduced in June 2026, aims to provide wallets with an interface to anonymity networks; a version supporting Tor and Nym was running on mainnet and was used by the Privacy Pools v2 web interface. For Bitcoin, the optional private-broadcast feature introduced in Bitcoin Core 31.0 sends transactions through Tor or I2P, using a separate connection for each transaction. A fallback that could expose an IP address after a failed anonymous handshake was disclosed in June 2026 and fixed in version 31.1.
- Flashnet: Flashbots presented this Ethereum anonymous-transaction submission research in February 2026. Its proposed design places transactions in randomized slots within shared batches and splits them across servers before reconstruction. The report said there was no production mainnet deployment or benchmark data yet, so its intended speed and privacy trade-offs cannot be compared as measured results.
OHTTP’s distinction is its default, relatively lightweight separation of who connects from what they request. It does not remove the need to trust that its operators remain separate, nor does it address every concern about dependence on large cloud providers. Zodl still allows users to switch to community nodes in advanced settings; the Ethereum Foundation’s discussion of anon-rpc, meanwhile, identifies centralized gateways’ ability to observe traffic or deny service as a separate risk.
