Ethereum co-founder Vitalik Buterin has introduced a “paranoid mode” designed to improve privacy when using AI agents. The experimental setup combines Tor routing, zkAPI payments, random cover traffic and local language-model prompt rewriting to reduce the information exposed during AI interactions. Buterin said the system is becoming usable, although latency and weaknesses against certain timing attacks remain significant limitations.
The approach addresses a growing concern as AI agents gain the ability to research information, interact with online services and perform tasks on behalf of users. These activities can reveal sensitive details through prompts, network connections and payment records. Buterin’s setup attempts to limit those exposures by separating conversations, masking request patterns and isolating the agent’s execution environment.
How Buterin’s Paranoid Mode Protects AI Agent Activity
A central feature assigns each conversation its own Tor circuit. Tor routes internet traffic through multiple relays, helping obscure a user’s network identity from the destination service. Separate circuits are intended to make it harder to link different conversations through their network routes, although they do not guarantee that activity cannot be correlated through other signals.
The system also introduces random cover traffic to make genuine requests less distinguishable from background network activity. Buterin described this protection as useful against passive observers, but acknowledged that it is weaker when an AI provider colludes with a Tor guard and actively manipulates or analyzes traffic timing. An observer able to compare timing patterns across different points in the connection may still identify relationships between requests.
Another component is zkAPI, which is intended to reduce identity exposure associated with payments for API access. Zero-knowledge techniques can allow a system to verify certain conditions without revealing all the underlying information. In this setup, the goal is to make it harder to connect payment activity with a particular user’s AI requests. Buterin also said cheaper deposit and withdrawal gas costs for zkAPI are expected to reach Ethereum mainnet, though the post does not provide a confirmed deployment date.
The setup rewrites prompts locally before sending them to an AI provider, using a locally supplied language model. Buterin said he was using Qwen3.8-Flash-Next for this part of the experiment. Local rewriting could help remove identifying details from requests, but its effectiveness depends on whether the model consistently recognizes sensitive information without changing the task’s meaning.
Execution isolation adds another layer. Buterin said the agent harness, identified as pi, runs inside a bubblewrap sandbox, with experiments also underway using microvirtual machines. Torsocks is used to route the agent’s connections through Tor. These controls can limit some forms of system access and network leakage, but the actual protection depends on configuration and on whether the software has vulnerabilities.
Latency and Timing Attacks Remain Unresolved
Buterin described the tool as increasingly practical for everyday research tasks, while noting that it adds substantial latency, particularly when starting a new conversation. Privacy mechanisms often introduce this trade-off because traffic routing, cover requests and additional processing consume time and resources. A system that is secure but frustratingly slow may be difficult for users to adopt for frequent AI tasks.
He also argued that Tor is not ideal for the strongest version of this use case. A more specialized mixnet could offer stronger protection by mixing traffic from different users and using constant cover traffic, making it harder to infer relationships from message timing. Such an approach may require considerably more bandwidth, creating another trade-off between privacy, speed and operating cost.
The experiment highlights a broader challenge for AI agents: protecting the content of a conversation is not enough if network metadata, API payments or execution behavior can still reveal a user’s identity. Buterin’s design combines several protections rather than relying on a single privacy technology. However, it remains an experimental setup, and the post does not establish that it has undergone an independent security audit or provides complete anonymity.
For the Ethereum community, the work connects privacy infrastructure with the growing use of autonomous AI software. If these tools become more reliable, users could gain greater control over how agents access external models and services. For now, the most important measures of progress will be independent security testing, resistance to traffic correlation, lower latency and clear evidence that the system reduces identity leakage in realistic conditions.















