What we build

Projects

Specifications, libraries and measurements. We take techniques that are too unproven for anyone to build on, make them run, and publish what they cost.

01

Origin

Hides who is asking, and the metadata that gives it away

  • anon-RPC

    In development

    The interface itself: a wallet integrates anonymised reads once, against a fixed API, and any anonymity network can serve them from behind it. The provider is a hash-pinned worker in an isolated sandbox with no access to keys, storage or the page.

  • tor-js

    Shipped

    The Tor Project's Rust client, Arti, compiled to WASM and embedded in the browser, so a wallet or dApp can route requests through Tor behind a fetch()-compatible API. Builds are reproducible: byte-identical WASM on x86_64 and aarch64 across three machines, so what you run is what was published.

  • KPS

    In development

    A WebRTC path between browsers and infrastructure that cannot present a CA-issued certificate, which is most of the network once you leave professional operators. An address is host, port and certificate hash, so running one needs no domain and no registrar. Interoperates across Go, Rust, JavaScript and the browser.

  • Access-Layer abstraction

    In development

    One interface between the edge and anonymity infrastructure, so Tor, Nym, HOPR, Nox and the rest are interchangeable behind a single API rather than five integrations.

02

Content

Hides what was asked: address, slot, access pattern

  • Sharded PIR

    Research

    A design that applies a different private-retrieval scheme to each slice of Ethereum state, because balances, code and storage have very different access patterns.

  • PIR specifications

    Shipped

    Executable reference specs for the Plinko, RMS24 and VIA schemes, with reusable lattice primitives, so an implementer starts from running code rather than a paper.

  • insPIRe on GPU

    In development

    Measuring what a private-retrieval server actually costs: throughput, latency, and the largest database one can serve, across GPU counts and query loads.

  • Universal PIR interface

    In development

    Middleware that hides PIR backends behind a stable schema, so wallets keep making ordinary Ethereum RPC calls while the schemes underneath keep changing.

03

Correctness

Hides nothing; it ensures the answer and its context are authentic

  • Binary trie clients

    Paused

    EIP-7864-ready execution clients, proven equivalent to mainnet inside a zkVM, which is what makes proofs small enough for a light client to check. A mainnet binary-trie node was built in Q2; the work is on hold since Q3 2026 following a team change, pending re-scoping.

Some projects keep their own site or repo as the source of truth. This page indexes them; it does not replace them. What each pillar covers and what the team does not do is on the about page; the argument for any of it is in Foundations.