Code
TorJS
Arti — the Tor Project's
Rust client — embedded in-browser by adapting and compiling it to WASM so any wallet, frontend, or dApp can route traffic through Tor
via a fetch()-compatible API. Now published as tor-js on npm. Built in collaboration with the Tor Project; upstream merge in progress.
Technical post / Integration docs (see also: high-level overview).
PIR Specs
Executable specs of Plinko & RMS24 schemes.
keewoolee/rms24-plinko-specReference specification for the VIA PIR scheme — covering VIA, VIA-B, and VIA-CB variants with reusable lattice primitives.
turanzv/via-specIn Development
Access-Layer abstraction: Edge ↔ Infra Transport Kit and interface
A pluggable interface between the edge (browser and native wallets, frontends, dApps) and anonymization-network infrastructure — for decentralized RPC access and beyond — with a WebRTC-driven transport kit as its foundation. The transport layer unlocks connectivity from the edge to a diverse range of infrastructure (PIR servers, anonymity-network nodes, Ethereum p2p nodes); the interface on top lets a diverse set of anonymity routing solutions [0] [1] [2] [3] [4] [5] plug in through a unified abstraction. Born from work on WebRTC connectivity between embedded Arti and the Tor network — and the realization that this stack is orthogonal and serves multiple use cases when abstracted and packaged cleanly.
insPIRe on GPU
GPU-accelerated benchmarking of the insPIRe scheme — measuring server throughput, latency, and the largest database size servable across varying GPU counts and query loads. Initial experiments (May 2026) show the vRAM blow-up in insPIRe is less than in OnionPIRv2.
Universal PIR Interface and Middleware
A middleware layer that abstracts PIR backends behind a stable GraphQL schema, so wallets and dApps keep using standard Ethereum RPC calls while PIR schemes and infrastructure evolve independently underneath.