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.
Adopters
Who's adopting anon-rpc
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.
Publishing a worker
Anonymizing networks
Each entry is live on Ethereum mainnet. 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.
tor-js
Anonymizing networkfetch 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.
Running a worker
Wallets & applications
The hosts (§2) that consume an anonymized fetch in production.
No shipping integrations listed yet. anon-rpc is a proposed standard, and the first wallet or application to ship it belongs here.
If you are building one, the integration is one class and one package — read the guide, then add yourself below.
Haven't integrated yet
Become an adopter
I run an anonymizing network →
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.
I build a wallet or app →
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.
Already integrated