As crypto privacy shifts to the network layer, how does Zodl leverage OHTTP to mask the 'who are you?' behind transactions?

Author: William M. Peaster, Bankless

Compiled by: TechFlow

TechFlow Summary: For years, encrypted privacy solutions such as zero-knowledge proofs have mainly obscured “what happens on-chain.” However, mobile light wallets still expose metadata like real IP addresses and access times to servers when requesting balances from nodes and broadcasting transactions, creating a backdoor for identity tracking.

With the Zcash wallet Zodl 3.20.0 defaulting to an OHTTP relay-splitting mechanism, the industry is addressing network-layer privacy gaps. Bankless outlines the latest defensive strategies and trade-offs from Zodl, Nym mixnets, the Ethereum Foundation’s Kohaku/anon-rpc, Flashnet, and the Bitcoin Core client.

Crypto privacy tools can mask everything you do on-chain, but identity-linked information can still quietly leak through off-chain metadata. The good news is this long-overlooked vulnerability is now receiving heightened attention across the entire industry.

For example, this week the Zcash wallet team formerly known as Zashi, Zodl, announced it is beginning to switch users to its entirely new, self-developed wallet server architecture. This architecture ensures your IP address and your wallet request data never fall into the hands of the same operator simultaneously. This feature launches with Zodl 3.20.0, ready out-of-the-box without manual configuration.

This is an exciting shift. A year ago, when I tested the Zashi privacy swap feature, its built-in Tor client was merely an opt-in add-on. Zodl, however, has now set network-layer protection as the default starting point.

Below, we will quickly break down the core principles of this new architecture and review other industry initiatives accelerating the prevention of network metadata leaks.

Your Exposed IP Address Is Betraying Your Identity

Most mobile crypto wallets are light wallets that do not store the full blockchain ledger locally. They rely heavily on remote servers to pull on-chain data and broadcast transactions, and those servers can clearly see your IP address, query request contents, and the exact timing of each request.

In the Zcash ecosystem, this task falls to the lightwalletd server. Even if your held ZEC has achieved full on-chain shielded encryption, these frequent connection footprints are still enough for seasoned analysts to piece together your identity and what you are doing.

This is far from paranoia; monitors specializing in this type of metadata already exist in the market. As early as 2023, developer b10c had publicly documented an entity called LinkingLion, which specifically tracked which Bitcoin nodes first broadcasted brand-new transactions.

This unique network-wide monitoring perspective means behind-the-scenes operators can precisely bind freshly minted BTC transactions to the real IP behind them. Furthermore, LinkingLion’s activity traces date back to 2018, implying they may have been secretly gathering connection intelligence for years.

The core issue is that this metadata tracking technology has long been applied to major crypto networks and even privacy coin ecosystems (for instance, b10c observed that LinkingLion’s same IP ranges also connected to Monero nodes). The industry urgently needs a completely new transaction routing foundation, which is exactly why Zodl is taking this step.

How Zodl’s New Privacy Server Operates

Before this, Zodl users looking to mask network metadata had only two options: either enable the slower Tor proxy, or unconditionally trust that the server operator would not act maliciously.

Zodl’s newly released solution introduces Oblivious HTTP (OHTTP). As a standard IETF internet protocol specification, OHTTP’s elegance lies in forcibly splitting a single network communication into two sequential segments, handing them to two independent parties to process, ensuring no single node can piece together the complete truth:

· Step one: Your local wallet encrypts every request using a key pair that only the ZODL gateway server can decrypt.

· Step two: The encrypted packets are sent to a relay server operated by Cloudflare or Fastly. Relay nodes strip the network headers containing identity information before forwarding them, so while the relay knows your real IP, it cannot read the content of your requests at all.

· Step three: The ZODL gateway becomes the only node along the entire path capable of decrypting the request ciphertext, then forwards the request to lightwalletd. ZODL can see what data you are querying, but the visitor address it sees is always just the relay server’s address.

In short, Cloudflare or Fastly knows “who is asking,” ZODL knows “what is being asked,” but no single party holds both pieces of information simultaneously.

Figure: Zodl’s privacy-split architecture based on the OHTTP protocol. Relay nodes only see the user’s IP, while the Zodl gateway only sees the request content (Source: ZODL)

This approach combines clever design with engineering practicality. Based on the publicly available open-source code, it also embeds two notable defense mechanisms: “traffic size padding” and “unlinkable logs”.

Regarding traffic characteristics, all outgoing requests are uniformly padded to fixed size tiers (in approximately 4 KB increments, with transaction broadcasts rounded up to 16 KB or higher), and sensitive responses follow the same method to prevent eavesdroppers from guessing whether you are querying a balance or broadcasting a transaction based on packet volume.

Regarding logging retention, request IDs generated by the relay layer are never written to ZODL logs in plaintext. The system only uses a dynamic key residing temporarily in the gateway’s memory to compute an HMAC fingerprint stored in the logs. Once the gateway restarts, the key is immediately destroyed. This means no one can align or correlate ZODL logs with relay logs afterward.

This codebase has just gone live, and Zodl will roll out updates to all users in batches over the coming days. Regardless, its arrival has broken the crypto industry’s silent inertia regarding naked network metadata exposure.

Trust Has Not Been Completely Eliminated

Objectively speaking, the effectiveness of the OHTTP privacy shield rests on one core premise: relay operators and ZODL must absolutely not collude. Additionally, relay servers can still detect when you go online, establish connections, and roughly how much traffic is transmitted; they simply cannot see the plaintext payload.

Therefore, critics on the Zcash Community Forum point out that since Cloudflare and Fastly are both US-based companies legally required to comply with judicial warrants, overhyping this mechanism might give some users a false sense of security.

In response, ZODL core contributor y4ss candidly replied and acknowledged this limitation, stating outright that OHTTP’s positioning is “a better default starting point, but it cannot replace Tor or Nym when facing powerful state-level adversaries.”

As y4ss previously suggested in discussions: if the legal pressure faced by underlying cloud infrastructure falls within your threat model, you can easily layer the Tor option in Zodl on top of OHTTP. In this setup, even the Cloudflare relay nodes would only see a Tor exit node IP, rather than your real address.

Despite its boundaries, the true victory of this system lies in achieving “default privacy.” Just like the vision David Hoffman cheered for when Ethereum launched the Kohaku privacy wallet in October 2025: privacy must be a factory-default standard, not an optional burden requiring manual tinkering from users.

Because OHTTP adds only a single lightweight relay hop, its minimal performance overhead is sufficient to support enabling it by default for all users.

Which Other Teams Are Pushing Forward at the Network Layer

Zodl’s progress is merely a microcosm of the crypto industry’s comprehensive crackdown on metadata leaks. Currently, various public chains and infrastructure teams are advancing along their own technical roadmaps. The highest level of protection, and indeed the most “heavily armored,” belongs to Mixnets.

In short, Mixnets scatter communication traffic and shuttle it between multi-hop relay nodes, padding all data packets to identical byte sizes while flooding the network with massive volumes of fake decoy packets, making it impossible for eavesdroppers to pair inbound and outbound traffic.

According to privacy project Nym’s September-disclosed updates, two Zcash wallets have already integrated its Mixnet: Zingo offers a one-click toggle, Zkool supports switching nodes to connect directly via the Mixnet, and Nym is currently exploring partnerships with Zodl.

Last week at Devcon 8, Nym also unveiled an entirely new SDK toolkit aimed at driving more wallets and decentralized applications into the Mixnet. The only obvious cost of this solution lies in speed, as multiple layers of obfuscation inevitably introduce latency.

Turning to the Ethereum ecosystem, the Kohaku privacy wallet project led by the Ethereum Foundation has listed IP and RPC leak prevention as core goals from day one. The newly launched Kohaku CLI tool now defaults to routing all traffic except self-hosted local RPC calls through Tor.

Meanwhile, the anon-rpc proposal put forward by the Ethereum Foundation this June aims to provide all wallets with a universal standardized interface for on-demand access to any anonymous network.

Versions supporting Tor and Nym are currently running live on mainnet, and the Privacy Pools v2 web interface has officially adopted it: users simply need to toggle on “Connect with Tor,” after which all RPC requests automatically route through the anon-rpc channel.

Another notable entry comes from Flashbots. Flashnet, introduced in February this year, is a cutting-edge research proposal targeting anonymous transaction submission for Ethereum. Users randomly fill shared batch slots with transactions and perform secret sharing, where shards are redistributed and reconstructed across a server cluster, thoroughly decoupling individual transactions from their senders.

Flashnet aims to sidestep two major pain points simultaneously: Tor’s relatively weak protection and Mixnets’ excessive latency. However, there are currently no official mainnet deployments or baseline stress-testing data released.

In the Bitcoin sector, developers have long worked to protect the “first hop” of transaction broadcasting. The Bitcoin Core 31.0 update launched in April this year added an optional private broadcast feature, allowing nodes to send transactions exclusively through Tor or the I2P anonymous network.

More importantly, each transaction opens a separate, independent connection channel, preventing outsiders from linking two different user transactions to the same network session.

This mechanism precisely targets the LinkingLion surveillance model mentioned earlier. However, the system is still undergoing real-world testing: in June this year, developers revealed a vulnerability where nodes would automatically fallback to the clearnet to retry if the anonymous handshake failed, thereby exposing the sender’s IP. This flaw was patched in version 31.1.

Figure: Comparison of speed and trust trade-offs for four network-layer privacy routing protocols: OHTTP, Tor, Mixnets, and Flashnet (Source: Bankless)

Summary and Outlook

So, does OHTTP qualify as the ultimate high-strength privacy solution? Clearly not on its own when facing resource-rich, state-level surveillance adversaries—an industry consensus reached long ago. But default configurations often reach the largest population of everyday users.

Allowing every Zodl user to seamlessly hide their real IP directly from their own wallet server backend without any cumbersome configuration inherently raises the industry’s overall privacy baseline.

Of course, the new contradictions arising from infrastructure dependencies also warrant close attention. The Ethereum Foundation’s anon-rpc documentation once flagged heavy reliance on cloud gateways like Cloudflare as a single point of failure, noting that these centralized gateways possess both the authority to inspect request traffic and the power to outright deny service; yet Zodl specifically selected Cloudflare to serve as half of its privacy-split architecture.

To be fair, these two designs target different risks: OHTTP focuses on restricting the information puzzle any single company can hold, whereas anon-rpc is more wary of who holds the power to arbitrarily cut off service. Furthermore, Zodl still allows users to switch back to community nodes via advanced settings.

Even so, if the default pathways for all future crypto privacy products end up resting on just a handful of cloud giants, this concentration risk remains significant and cannot be underestimated.

It remains to be seen whether other mainstream wallets will quickly follow Zodl’s default configuration strategy. Regardless, the industry’s evolutionary direction could not be clearer: the frontlines of crypto privacy have officially expanded toward the network transport layer, which currently cries out for the most urgent improvements.