Passthrough
Reference workerplain fetch (no anonymization)
The minimal reference worker: it fulfils calls with an ordinary fetch, so requests are not anonymized. It demonstrates the sandbox and hash pinning, not privacy.
anon-rpc has two sides. An anonymizing network publishes its client as a
hash-pinned worker and points a specifier contract at it. A wallet or app
passes that specifier address to a harness and gets back an anonymized fetch.
Each entry is live on Ethereum mainnet unless badged as a testnet. The specifier address is everything a wallet needs — paste it into a harness and the pinned client code is fetched, hash-verified and sandboxed for you.
plain fetch (no anonymization)
The minimal reference worker: it fulfils calls with an ordinary fetch, so requests are not anonymized. It demonstrates the sandbox and hash pinning, not privacy.
fetch over Tor
Runs a full Tor client compiled to WebAssembly inside the sandbox, building circuits in the browser. Expect a bootstrap delay before the first response, and higher per-request latency than a direct fetch, since traffic is relayed through multiple hops.
Demonstration gateway only: limited capacity, and it may disappear at any time — run your own for anything real. Browsers cannot open the raw TCP that Tor uses, so gateways act as blind KPS relays into the Tor network.
fetch over the Nym mixnet
Runs a Nym mixnet client compiled to WebAssembly inside the sandbox. Requests travel as Sphinx packets through the mixnet and leave at a Nym IP Packet Router, so the RPC endpoint sees the router's address, not yours. The bundle is about 18 MB and the mixnet takes a few seconds to bootstrap.
fetch over a Sphinx mixnet
Wraps each request in Sphinx packets routed through entry, mix and exit nodes, dialled over KPS. TLS to an https RPC runs inside the worker, so the exit node relays the request without reading it. Mixing adds per-hop delay, so expect slower responses than a direct fetch.
The hosts (§2) that consume an anonymized fetch in production.
Private deposits, transfers and withdrawals on Ethereum and L2s. Its web app can route every RPC call through anon-rpc when users turn on Connect with Tor in the RPC settings, so the RPC provider never sees the address the call came from. Off by default, and the user picks the gateway.
A link aggregator for crypto and the open web. Its website reads Optimism and Ethereum mainnet through anon-rpc when readers turn on the anon-rpc switch in Settings. If an RPC provider refuses Tor traffic, it fails over to the next provider.
Ship your client as a hash-pinned worker and point a specifier contract at it: the capability API, the bundle, and hosting the bytes. Every wallet using anon-rpc can then reach you by address alone.
Construct a worker from a specifier address and get back an anonymized fetch.
One class, one package — and switching networks later is a change of address.