Anon-RPC Standard for Anonymized Wallet Reads on Ethereum

Andrew from the Ethereum Foundation discusses privacy concerns with RPC providers during a presentation on privacy and consent. Even when funds remain private, RPC providers can link queried addresses to user IP addresses and to each other. To break this link without requiring a separate SDK for every wallet and network pair, the speaker introduces anon-rpc. In this system, a network publishes its client on-chain as a single hash pinned javascript bundle. Wallets or applications fetch these bytes from advisory resolvers, verify the hash, and run them inside a web worker within a null-origin iframe. This setup features a small capability API providing scoped storage and direct network node access via KPS, an optional transport that improves censorship resistance by avoiding certificate authorities and DNS. The session covers content-addressed code with on-chain update governance, browser sandboxing properties, and trust considerations. A specification, an MIT implementation, and a mainnet demo for running tor-js are currently available.