atmos

atmos

Anonymous Ethereum RPC that is fast enough to leave on.

Run it on your machine

curl -fsSL https://atmos.xavio.dev/install.sh | sh

Then add this to MetaMask as a Sepolia network

http://127.0.0.1:8545/11155111

Needs Node 24 or newer. Install guide

Faster, verified, private: measured

Stock anon-rpc against Atmos, from the cloud. The same wallet-shaped workload runs in each setup: plain RPC, the stock anon-rpc Nym worker, and Atmos on top of that same worker, with and without verified reads and a constant-rate schedule. The ideal is a truly anonymous RPC: as fast as plain RPC, every answer proven, and nothing learned about who, when or what.

Faster

Speed details ↓

5.5–6.6× faster page load than stock anon-rpc

Ten parallel reads, median per region: Atmos 2.7–3.6 s, stock anon-rpc 14.7–22.0 s, plain RPC 0.19–0.60 s.

Plain RPC
Stock anon-rpc
Atmos
0.1 s0.3 s1 s3 s10 s30 s 24 s cut-off
Each square is one session (4 per region, 3 regions). A hollow square is a session whose burst hit the 24 s cut-off, so stock's real time is longer.
  • Against plain RPC, a call costs about 0.5–0.6 s more: the mixnet round trip.
  • The slowest 5% of steady calls are 3–5× faster than stock.
  • A single typical call is only 1.2–1.7× faster; the gain is in parallel reads.

10-read burst, Atmos v1 in the browser harness · Cloud Run, 3 regions × 4 sessions · 2026-11-06 · bench:v9 (94f519b)

Verified

Verification details ↓

7 methods proven against a light client; stock anon-rpc proves none

For a proven method, a lying provider or exit can cause a failure, never a wrong answer.

  • eth_blockNumber
  • eth_getBalance
  • eth_getTransactionCount
  • eth_getCode
  • eth_getStorageAt
  • eth_call
  • eth_getTransactionReceipt
  • eth_chainId
  • eth_sendRawTransaction
  • eth_estimateGas
  • eth_getBlockByNumber
  • eth_getBlockByHash
  • everything else

proven checked, not proven: a local constant, and a transaction hash that must match partly: the gas figure and a block's transaction list are the provider's sent plainly, and counted

  • A verified balance costs about 0.5–0.9 s more than an unverified one.
  • The latest block number takes 0 ms: it is answered from the verified head.

The SDK and the host · Sepolia sync-committee light client · in the benchmark, eth_call, eth_estimateGas and receipts passed through unchecked

Private

Privacy details ↓

52% chance is 50%: an observer of outgoing requests can't tell busy from idle

With shaping on, from the request count. From bytes it was 60%, not significant.

chance 0%50%, chance100% shaped: 52.1%not shaped: 98.6%by request count
  • Who Hidden from the providerIt sees a Nym exit, not your IP. Only the Nym directory and your entry gateway see it.
  • When Hidden only with shaping, which is opt-inOff by default; turn it on with shape: true or ATMOS_SHAPE=1. Outgoing requests then leave on a fixed clock. Replies are not padded.
  • What Not yetProviders still see which accounts you query. The access-list mode (experimental) hides repeat reads while it keeps pace.

atmos-host, local sessions (2–4 hosts), 12 s windows, best single-threshold observer · outgoing requests only, replies not measured · not the cloud run

The first answer is slower. Atmos took 17–71 s to its first answer across setups and regions, against 16–33 s for stock anon-rpc. Why

Faster

Four sessions per arm on publicnode and mevblocker, one image for every arm, with the arm order rotated per task. Measured 2026-11-06.

Results, europe-west1

ArmSessions10-read burstSteady p50Steady p95First answerSuccess
Direct fetch (not anonymous)4185 ms
104 ms – 244 ms
36 ms56 ms122 ms100%
Stock anon-rpc, Nym worker417.9 s
12.0 s – 24.0 s
915 ms3.2 s15.9 s100%
Atmos v1, browser harness42.7 s
2.2 s – 3.3 s
538 ms1.0 s26.7 s100%
Atmos v1, Node harness42.7 s
1.2 s – 2.7 s
554 ms889 ms19.3 s100%
Atmos with verified reads42.7 s
2.0 s – 4.0 s
0 ms1.3 s36.2 s100%
Verified reads, as the self-hosted endpoint runs them42.9 s
2.5 s – 3.8 s
0 ms1.5 s29.3 s100%
Atmos with a constant-rate schedule47.7 s
6.8 s – 8.5 s
2.0 s2.5 s16.9 s100%

Burst values are the median across sessions, with a bootstrap 95% interval underneath. Steady latency is per call during the polling phase. "First answer" runs from creating the worker to its first successful reply, boot included.

Page-load burst: when each of 10 parallel reads finished
  • Direct fetch (not anonymous)
  • Stock anon-rpc, Nym worker
  • Atmos v1, browser harness
Show as a table
ReadDirect fetch (not anonymous)Stock anon-rpc, Nym workerAtmos v1, browser harness
1165 ms4.81 s2.67 s
2165 ms10.31 s2.67 s
3166 ms10.78 s2.67 s
4166 ms11.36 s2.68 s
5166 ms12.30 s2.68 s
6168 ms12.40 s2.68 s
7170 ms13.82 s2.68 s
8170 ms14.06 s2.68 s
9172 ms15.23 s2.68 s
10174 ms17.13 s2.68 s

A call with no answer after 24 s is cut off. In this run the stock worker's median session answered all ten burst reads before the cut-off, one after another, over 17 s; in earlier runs most of them hit it.

The staircase is the cost of parallel calls through one stock worker. Its transport keeps a single pooled connection per origin, so every extra concurrent call opens a fresh TCP and TLS connection through the mixnet, one after another. Atmos sends the same ten reads as one JSON-RPC batch on a connection that is already warm.

Three regions

The final run: every arm on one image, Cloud Run in three regions, 4 sessions per arm per region, 10-minute sessions. Each cell is the burst median, then steady p50 and the share of calls answered. A steady p50 of 0 ms for verified reads is eth_blockNumber answered from the verified head.

RegionDirectStock anon-rpcAtmos v1Atmos, Node harnessVerified, self-hosted
europe-west1185 ms
36 ms · 100%
17.9 s
915 ms · 100%
2.7 s
538 ms · 100%
2.7 s
554 ms · 100%
2.9 s
0 ms · 100%
us-east1271 ms
85 ms · 100%
14.7 s
709 ms · 100%
2.7 s
603 ms · 100%
1.5 s
579 ms · 100%
3.9 s
0 ms · 99%
asia-south1596 ms
210 ms · 100%
22.0 s
1.2 s · 100%
3.6 s
841 ms · 100%
2.1 s
874 ms · 100%
5.8 s
0 ms · 100%

When a route stalls, Atmos switched to its standby 14.7–18.3 s later, and each session lost only the one call in flight (run 4).

Against direct RPC, per method

The parity run: steady calls only, 4 sessions per arm per region. Each cell is p50 / p95. Atmos adds about 0.5–0.6 s per call, which is the mixnet's round trip, and a verified balance adds about another 0.5–0.9 s for its proof. The latest block number is answered from the verified head.

RegionMethodDirectAtmos v1Verified
europe-west1eth_blockNumber37 ms / 64 ms542 ms / 1.6 s0 ms / 1 ms
europe-west1eth_getBalance37 ms / 57 ms584 ms / 1.6 s1.2 s / 3.9 s
us-east1eth_blockNumber121 ms / 152 ms672 ms / 2.0 s0 ms / 1 ms
us-east1eth_getBalance124 ms / 175 ms674 ms / 1.6 s1.1 s / 3.4 s
asia-south1eth_blockNumber161 ms / 270 ms769 ms / 2.5 s0 ms / 1 ms
asia-south1eth_getBalance162 ms / 271 ms767 ms / 2.7 s1.7 s / 4.9 s

In the benchmark, eth_call, eth_estimateGas and receipts pass through the verified arm unchecked; the self-hosted endpoint runs eth_call locally on proven state, which is measured separately.

Time to the first answer

This is where Atmos is slower than the stock worker. Before its first answer, Atmos loads the Nym directory, tests a gateway, and checks the route with a real call; verified reads also sync a light client. Medians per region (europe-west1, us-east1, asia-south1):

Stock anon-rpc15.9 s · 16.8 s · 32.8 s
Atmos v1, Node harness19.3 s · 35.9 s · 54.2 s
Verified reads, as the self-hosted endpoint runs them29.3 s · 52.2 s · 71 s

Across all Atmos arms and regions, the first answer took 17–71 s, against 16–33 s for the stock worker.

Browser or Node

The same client, with the anonymity worker in headless Chromium or in Atmos's Node harness (a V8 isolate, no browser). Run 7 adds the pinned worker hash and the worker's host allowlist: 8 of 8 boots passed under both.

10-read burstSteady p50Steady p95Answered
Chromium (atmos-run5)2.8 s522 ms746 ms100%
Node harness (atmos-run5)3.4 s572 ms759 ms100%
Chromium, pinned hash and allowlist (atmos-run7)2.5 s570 ms1.4 s100%
Node harness, pinned hash and allowlist (atmos-run7)4.0 s656 ms1.7 s100%

Optional settings

Four sessions each. None beat the defaults by more than the spread between sessions, so all stay off in the client; the self-hosted endpoint turns on rotation (every 10 minutes) because it limits how long one route's timing lasts.

10-read burstSteady p50Steady p95Answered
Atmos v1, defaults2.6 s542 ms918 ms100%
Hedged reads2.5 s579 ms1.0 s100%
Route rotation every 2 minutes2.6 s631 ms1.1 s100%
More reply SURBs2.4 s616 ms1.1 s100%
15 s exit connect timeout2.6 s687 ms1.1 s100%

Earlier reference: run 2

Six sessions per arm per region, 10-minute sessions, sessions on flashbots left out. A stock burst of 24.0 s means the median session hit the 24 s cut-off.

RegionDirectStock anon-rpcAtmos v1
europe-west1195 ms
37 ms · 100%
24.0 s
1.2 s · 96%
2.3 s
746 ms · 100%
us-east1326 ms
81 ms · 100%
18.8 s
1.2 s · 100%
3.3 s
826 ms · 100%
asia-south1662 ms
154 ms · 100%
24.0 s
2.1 s · 93%
3.0 s
1.1 s · 99%

Earlier measurements

Before this benchmark, the same effect was measured in a desktop browser with live Nym workers. Those runs used a home connection and few samples, so read them as direction, not as final figures.

Pattern, 10 reads on one workerWall time (3 rounds)
10 concurrent calls (how wallets issue them)8.5 / 9.1 / 9.9 s
10 sequential calls6.7 / 6.8 / 7.0 s
One JSON-RPC batch1.06 / 1.20 / 1.45 s
Two 5-read batches on two workers0.83 / 0.89 / 0.99 s

Verified

Verified reads

Every read checked against a light client, in europe-west1. Refreshing the verified head on a fixed clock, and reusing proofs within a block, made the burst about four times faster.

10-read burstSteady p50Steady p95Answered
Before (atmos-run3)13.6 s1.8 s5.9 s100%
After (atmos-run6)3.5 s0 ms1.4 s100%

p50 is 0 ms because most steady calls are eth_blockNumber, answered from the verified head; verified reads alone are 0.9–1.4 s.

Private

What an observer can tell

An observer of the self-hosted endpoint's outgoing traffic tried to tell 12-second windows of wallet activity from idle ones, with the best threshold chosen with hindsight. 50% is chance. This covers outgoing requests only: replies are not padded, and incoming traffic has not been measured.

From request countFrom bytesFrom head checks
Shaping off98.6%98.6%51.4%
Shaping on52.1%60.4%50%

Method

The workload

One session takes about ten minutes, on one RPC provider chosen per session:

  1. Boot. Create the worker; time to ready, then to the first successful call.
  2. Page-load burst. Ten reads at once: eight eth_getBalance, one eth_blockNumber, one eth_getTransactionCount.
  3. Steady polling. eth_blockNumber every 12 s and a balance every third tick. Three times per session, one eth_call, one eth_estimateGas and one receipt lookup.
  4. Write. One unfunded Sepolia transaction from a fresh key. The expected answer is insufficient funds, so the write path is measured without moving value.

How sessions are compared

  • The unit is the session, not the call, since calls within a session are correlated.
  • Arms are interleaved in each region, with the order rotated per task, so drift over time and the cost of a cold start hit every arm equally.
  • The direct arm is each region's own floor. Latency added by the anonymity network is reported against it, within the same region.
  • Only keyless public RPCs are used, at a few requests per second per provider at most.

This run

  • Run atmos-final, 2026-11-06; sessions ran 21:50–23:09 UTC. Executions: europe-west1 atmos-final-zpgmf, us-east1 atmos-final-5m8dl, asia-south1 atmos-final-bzqh9.
  • Image bench:v9, built from commit 94f519b. Cloud Run, 2 vCPU and 4 GiB per task.
  • 4 sessions per setup per region, 10-minute sessions, the setup order rotated per task. Providers publicnode and mevblocker (keyless); a call with no answer after 24 s is cut off.
  • The unit is the session: medians, with bootstrap 95% intervals.
  • Every session, 84 in all (3 regions × 7 setups × 4): CSV · JSON with the run details.