Your RPC provider sees too much: a standard for anonymized wallet reads

Duration: NaN:NaN:NaN

Speaker: Andrew

Type: Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

Even when funds are private, metadata isn't: the RPC providers behind most wallets can link the addresses you query to your IP and each other. Anonymizing networks can break that link, but shipping one SDK per wallet×network pair doesn't scale. anon-rpc inverts this: a network publishes its client on-chain as a single hash pinned js bundle. Wallets (or apps) fetch the bytes from advisory resolvers, verify the hash, and run them in a Web Worker inside a null-origin iframe with a small capability API providing scoped storage and direct access to network nodes via KPS. Using the optional but encouraged KPS transport improves censorship resistance by avoiding certificate authorities and DNS. The talk teaches the transferable parts: content-addressed code with on-chain update governance, browser sandboxing properties, and where trust still sits. Spec, MIT implementation, and a mainnet demo for running tor-js exists today. https://privacy-ethereum.github.io/anon-rpc/