A different route to the wallet server

ZODL said on 9 November that it was beginning a gradual rollout of its own Zcash lightwallet infrastructure using Oblivious HTTP, or OHTTP. Its announcement names Cloudflare and Fastly as independent relay providers and identifies Zodl 3.20.0 for Android and iOS as the starting point. F-Droid and GitHub releases were described as following later that week; NetNapz has not independently confirmed their completion.

Lightwallet servers help a wallet synchronize with the blockchain and relay transactions. A direct connection can expose a user’s IP address alongside request metadata, even where transaction details are shielded. Under the announced arrangement, the relay receives the user’s connection but forwards encrypted requests; ZODL processes their contents without receiving the originating IP address. The company also says operating its own servers gives it more direct control over reliability and capacity. Those are operational aims, not independently measured performance results.

Separation is conditional, not universal anonymity

The IETF’s RFC 9458 explains the protocol’s division of knowledge: the relay handles encrypted messages, while the gateway decrypts them. Its privacy design requires separate relay and gateway operators. The standard also warns that timing and message sizes can support traffic analysis; encryption alone does not eliminate those signals. Request contents that identify a client can create linkage at the application layer.

In the announcement’s technical discussion, a ZODL participant explicitly acknowledged that OHTTP is not a substitute for Tor. The participant said relay–gateway collusion, including legal pressure on both, could defeat the separation. Tor remains supported and can carry the OHTTP traffic, so the relay sees a Tor exit rather than the user’s original address.

The same discussion says sensitive responses are padded and streamed block data uses encrypted chunks. It also limits these particular relays to Zodl mobile-app requests rather than general browser clients. These are implementation descriptions from the developer, not an independent security audit or proof of universal deployment.

NetNapz assessment: a better default with a specific boundary

The useful change is reducing the information one routine infrastructure operator receives by default. That is narrower than concealing every network trace or guaranteeing anonymity against coordinated observers. Wallet users should distinguish this transport-layer measure from transaction shielding and from a Zcash consensus upgrade. The announcement establishes neither a new right for ZEC holders nor a basis for claiming a token-price effect.

NetNapz checked the public announcement, its follow-up discussion and the protocol standard. We did not open a wallet, connect funds, test relay traffic or verify the percentage of users migrated. The rollout’s actual reach and operational performance remain separate questions.