Register and share your invite link to earn from video plays and referrals.

raulk
@raulvk
p2p, agents, wasm, distsys, ethereum | prev: p2p networking & scaling @ethereumfndn, @protocollabs, @redhat
Joined February 2008
722 Following    5.3K Followers
Privacy should be the universal default, not a cypherpunk flag. Every on-chain read and write leaks metadata to multiple observers: ISP, DNS, RPC, indexer, bundler, chain. Hermetic is a modular playground for access-layer privacy. Still very alpha. A self-contained local binary that stacks privacy-preserving layers and exposes sound solutions, with stated tradeoffs, over simple APIs. Today: - Railgun shielding, unshielding, queries. - Every egress request over an isolated Tor circuit, including DNS (next: DoH). - Rust host + embedded Tor via Arti, no separate sidecar. How: - SDK code runs sandboxed in @deno_land, stripped of most permissions. - No fetch, no node:net, no host writes. Modules are cut off from the world. Untrusted. - Every SDK network call crosses the Deno boundary, Hermetic intercepts and routes via Tor. No escape possible. Doesn't yet defend against broadcaster trust, query-pattern inference, timing leaks, or mempool exposure. Exploring: - Aztec and other on-chain privacy backends. - Wasm modules, light clients, messaging. - Account isolation. - Local, agent-friendly APIs. Would appreciate help. DM if interested!
Show more