What is shipping

Roadmap

01

Origin

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

Anonymous RPC

Arti, the Tor Project's Rust client, compiled to WebAssembly and running in the browser, so a wallet or dApp can reach Ethereum without handing its network location to whoever answers.

Now

  • Wallet, SDK and light-client integrationsQ3 2026

    Integrating tor-js upstream by pull request, with ethers.js as the first target and dependent wallets after it.

  • Upstream to the Tor ProjectIn progress

    The WASM compatibility work merging back into Arti itself, so the browser build stops being a fork.

  • WebRTC transportQ3 2026

    A transport that browsers can actually dial, for infrastructure that cannot present a CA-issued certificate.

Next

  • Broader SDK and light-client rolloutQ3 2026

    Past the first integration, into the clients that depend on it.

  • Messenger protocol surveyQ3 2026

    What the messaging world already solved for metadata resistance, and what transfers.

Later

  • External security auditQ3 2026

    Independent review before anyone should depend on this in production.

  • Edge-to-P2P transaction broadcastingQ3 2026 and beyond

    Sending a transaction without the first hop learning who sent it.

  • Hybrid post-quantum key exchange

    Undated. Tracked because the anonymity guarantee has to outlive the transport.

Access layer

One pluggable interface over anonymity networks, so the edge can swap Tor for a mixnet or anything else without the application changing. The same shape extends to reaching peer-to-peer networks generally.

Now

  • Architecture and the anon-RPC standardIn progress

    Published as "Power to the Edges", with a draft standard and a browser demo you can run.

Next

  • Unified WebRTC transport specQ3 2026

    One transport spec that works in the browser and in Node, with standardised validation of the WASM binary.

  • Pilot deploymentQ3 2026

    The wallet to Tor to execution-node path, exercised end to end by somebody outside the team.

Exploratory

  • Formal methodsQ3 2026

    Lean-based verification starting from rustls-rustcrypto primitives and our PIR cores, with Leo Alt at Powdr Labs.

  • Privacy-preserving RPC aggregation

    With the Protocol State team: an aggregation layer that strips addresses and mixes queries, alongside the anonymity-network path.

02

Content

Hides what was asked: address, slot, access pattern

Private retrieval

Retrieval schemes matched to the shape of Ethereum state, so a server can answer a query it cannot read. Different slices of state have very different access patterns, so they get different schemes.

Now

  • PIR GenesisQ4 2026

    The first end-to-end deployment over live Ethereum state: a sharded system behind versioned middleware that routes each call to the right shard, with two inaugural shards. First demo is an ETH balance retrieval.

  • Reproducible benchmarksOngoing

    Independent replication of the setups papers report, plus standardised database, entry and hardware configurations so numbers can be compared.

Next

  • Skirrt batch retrievalIn progress

    An in-house double-stateless batch scheme that fetches a whole Merkle proof in one batched query, with an order of magnitude less communication than prior batching. Paper and reference implementation in progress.

  • GPU scale-upQ3 2026

    Side-by-side GPU benchmarking of VIA, insPIRe and OnionPIRv2 with the SNU SCALE lab.

Later

  • End-to-end sharded retrievalH2 2026

    At least two shards covering at least two slices of Ethereum state, running together.

  • Archival-state snarkificationQ3 2026

    Shrinking the database so the server can be smaller, which is most of the cost.

  • Retrieval and statelessness2027

    What happens when the nodes serving state stop holding it, which is the same force that motivates all of this.

  • Incentivised state serving2027 and beyond

    Micropayments or another incentive layer for serving reads, so doing it well is worth doing.

03

Correctness

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

Verifiable binary trie

An execution-layer node running a binary trie (EIP-7864) and provably equivalent to mainnet, so retrieval servers, wallets and light clients can consume binary state before the protocol adopts it.

Paused since Q3 2026 following a team change. A mainnet binary-trie node was built in Q2; the work is on hold pending re-scoping.

Now

  • Binary-trie sidecar on GethPaused

    A Geth-based node syncing mainnet. Blocked on inefficient binary conversion, with upstream optimisation underway.

  • Binary trie on EthrexPaused

    Initial implementation contributed via Lambda. Sync stable on Hoodi as of April 2026.

Next

  • Shadow-chain sync to mainnetPaused

    Full mainnet sync producing state roots equivalent to the canonical ones, block by block.

  • zkVM proving of state transitionsPaused

    Recursive proof that binary-trie updates match the canonical updates.

  • Binary trie into retrievalPaused

    Retrieval servers using provable binary state without trusting the node operator.

11 items carry a date that has passed. They are struck through until the next planning cycle confirms whether they landed. Why any of this is worth doing is in Foundations; what the team does not do is on the about page.