Vitalik's paranoid mode, in a browser tab
Ask in
the flock.
Ask AI while sharing less of yourself. Rewrite on your device, route through a mixnet, and keep your identity out of the conversation.
Move your cursor through the flock. Try to follow one bird.
How it works
Four layers, one tab.
Each layer hides something different. Take one away and the others still hold.
-
01
Rewritten on your device
Rewrite identifying details locally, then review what will be sent.
WebLLM · Qwen3 · WebGPU
-
02
Mixed on the way out
Layered encryption, mixing delays and cover traffic help obscure the route your question takes.
Nym mixnet · mixFetch
-
03
Paid without a name coming soon
Prove you have credit without attaching your payment identity to each question.
zkAPI design · Groth16 · Solana
-
04
Forgotten between chats
Fresh credentials for each conversation. History stays in your browser.
Per-chat identity · Local-only storage
Who sees what
Same question. Very different trail.
| Your IP address | Your exact words | Who you are | Which chats are yours |
|---|
sees it partly can't see it
Less identifying. Still your question.
Your question.
With less of you attached.
An illustrative rewrite. Review and edit yours before sending.
My landlord Dave in Leeds won’t return my deposit. What are my options?
Example only · nothing is sentThe path of one question
From your keyboard to an answer.
Follow the request, step by step +
Payment rides with the question: a zero-knowledge proof tells the gateway “someone with credit is paying” and nothing else. After the answer, the gateway signs a refund for whatever the reservation didn't use, and that signature is your next balance.
Compared with the original
His setup, rebuilt for the browser.
Vitalik Buterin runs zkAPI, Tor, cover traffic and a local rewriter behind a sandboxed agent. Here's how each piece maps to a web page.
Explore the technical comparison +
| Protection | Vitalik's paranoid mode | Murmur, in the browser | |
|---|---|---|---|
| Anonymous payments | zkAPI on Ethereum through a local daemon | The zkAPI design on Solana, pay-per-use with refunds; proofs are generated in the tab, withdrawals are verified on chain | Solana |
| Local prompt rewriting | His own local model | WebLLM runs Qwen3 on your GPU; the original stays in the page | On device |
| Network privacy and cover traffic | Tor plus random cover traffic | Nym mixnet with mixing delays and constant cover traffic, the kind of network he said this needs | Nym mainnet |
| Separate conversations | A Tor circuit per conversation | A fresh payment key and isolated history per chat, over a mixnet that unlinks every packet | Per chat |
| Agent sandbox | bwrap or a microVM | Murmur runs no agent and has no tools that touch your computer, so there is nothing to sandbox | Not needed |
Know before you deposit
The trade-offs, stated plainly.
Payments are next
The vault, the proofs and the refunds are built and tested; they open to the public after the setup ceremony. Until then every question goes to the free model and costs nothing. When payments open, a deposit or withdrawal costs well under a cent in fees and each answer is charged at its actual cost.
Keep your backup code
Your balance is a secret in this browser, not an account. The app gives you a backup code; lose it and nobody, including us, can recover the balance. Never restore it on two devices at once: spending the same ticket twice reveals the secret and voids the note.
Not in Tor Browser
Tor Browser turns off WebGPU, which the local rewriter needs. Use a normal browser; the mixnet takes Tor's place.
Collusion still hurts
The mixnet resists timing attacks far better than Tor. A model provider working with many mix nodes at once could still learn something.
It's slower
Mixing adds seconds per request, a proof takes a moment, and the rewriter model is a one-time 0.4–2.3 GB download. Privacy costs latency.
The rewriter isn't perfect
A small model can miss a detail or change your meaning. Murmur always shows you exactly what will be sent, flags anything that survived, and lets you edit it first.
Questions
Asked, anonymously.
Does anything leave my computer before I approve it?
No. The rewrite happens on your GPU. You see the rewritten text and can edit it before sending. Only that version is ever transmitted.
Which AI answers my questions?
Today, a free hosted community model. Next, paid access to stronger models (OpenAI, Mistral, DeepSeek and more), each question paid from a private balance with a short-lived key the operator issues against a proof, plus the option to point the app at your own endpoint.
How will I pay?
Payments are coming soon and will work like this. The app gives you a one-time Solana address. Send USDC to it from any wallet or exchange; when it arrives, it becomes a private balance in the vault. No wallet connection, no account, no SOL needed; the network fee is on us. The address that funded a note is visible on chain, like any deposit; what is not visible is which questions, if any, are yours. Each answer is charged at its actual cost and the rest of the reservation comes straight back, signed. Withdraw the remainder to any address you type.
Why a mixnet instead of Tor?
Tor routes packets quickly but doesn't reorder or pad them, so someone watching both ends can match timing. A mixnet delays, shuffles and pads traffic. Vitalik made the same point: this needs a mixnet with constant cover traffic.
What happens to my chats?
They're stored only in your browser, each with its own identity. Delete a chat and it's gone; there is no server copy.
What does it cost?
Nothing today: the rewriter runs on your hardware, the mixnet is free to use and the community model is free. When paid models open, questions will cost the model's price, measured per answer and taken from your deposit, with Solana fees on us.
Community token · Solana
$MURMUR
The token of the flock, on Solana. Utility launching soon.
Not financial advice. Only ever use the contract address shown on this page.