atmos

Anonymous Ethereum RPC that is fast enough to leave on.

atmos.xavio.dev · a client layer on top of anon-rpc

The problem

Your RPC provider knows who you are and what you hold

Who

Every call carries your IP address.

What

Every balance you check names an address, and an address is an identity.

anon-rpc today

Private, but slow where wallets need speed

anon-rpc routes a wallet's calls through the Nym mixnet from a sandboxed, hash-pinned worker. The provider sees an exit, not you. But a page load fires many reads at once, and each one waits for its own fresh connection through the mixnet.

14.7–22.0 sten parallel reads, stock anon-rpc
0.19–0.60 sthe same reads over plain RPC

Median per region, Cloud Run in 3 regions, 4 sessions each, 2026-11-06

Atmos

Faster, verified, private

5.5–6.6×Faster

page load than stock anon-rpc; the slowest calls 3–5× faster

7 methodsVerified

proven against a light client: a lying provider causes a failure, never a wrong answer

52%Private

an observer's accuracy at telling busy from idle, with opt-in shaping (chance is 50%)

Speed: Cloud Run, 3 regions, 2026-11-06. Privacy: local host sessions, outgoing requests only.

How it works

Same worker, same trust model, a better client

A request leaves the wallet through the local host, the SDK and the sandboxed Nym worker, then crosses the entry gateway, three mix layers and the exit to the RPC provider. The reply comes back on its own route. A standby route stays warm.Nym mixnetWalletLocal host127.0.0.1:8545Atmos SDKroutes, batches, checksNym workeranon-rpc's sandboxEntryMix 1Mix 2Mix 3ExitIPRRPC providerstandby route, warm · routes rotate about every 10 minutes
request reply, on its own reply path · only the Nym directory and the entry gateway see your IP; the provider sees the exit

Verified

Proven, not trusted

Sync-committee signatures give a verified head; its state root checks the provider's proof; only then does the answer reach your code. A wrong proof ends in a failure, never a wrong answer.Sync committeesigned by 512 validatorsVerified headlight clientState rootin that headerProof checkedeth_getProofAnswerto your codeRPC provider sends the valueand its Merkle proofeth_call runs in alocal EVM on proven statea proof that does not match:a failure, never a wrong answer

Balances, nonces, code and storage by eth_getProof; eth_call in a local EVM on proven state; receipts against the receipts root. A proof costs about 0.5–0.9 s.

Node harness

The Nym worker, without a browser

  • Forkedanon-rpc's Node harness, extended with the browser pieces the Nym worker needs (WebSocket, Blob, Worker, MessageChannel), inside a V8 isolate
  • FixedWebAssembly that never finished loading, and a WebSocket bridge that sent empty frames and silently broke every mixnet handshake
  • ResultTen parallel reads in 1.5–2.7 s, as fast as Chromium (2.7–3.6 s)

Same client in both; Cloud Run, 3 regions, 4 sessions each, 2026-11-06

Hardened

Closing what IP hiding leaves open

  • Silent bootThe worker hash is pinned: starting sends no RPC call from your IP, and a lying provider can't swap the worker
  • ConfinedThe worker can reach only the Nym directory and its entry gateway; everything else has to cross the mixnet
  • Local onlyThe host answers localhost and wallet extensions; websites and DNS rebinding are refused
  • AuditedRedirect checks, entropy, WebSocket floods, trusted block hashes, EVM fork rules: found and fixed, each with a test

A traced boot made 0 RPC calls; a hostile worker's direct calls were refused

Demo

Verified Sepolia reads, from a browser tab

The SDK starts in the page, joins the mixnet, verifies the chain head and answers reads with proofs. No Atmos server is involved.

The first answer takes 15 to 70 seconds while the worker joins the mixnet.

Install

One line for MetaMask

Run the host on your machine

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

Then add this RPC URL as a Sepolia network

http://127.0.0.1:8545/11155111

Or in your own app: the SDK's createAtmos() is an EIP-1193 provider for viem, ethers and wagmi.

The numbers

Ten parallel reads, per region

RegionPlain RPCStock anon-rpcAtmos
europe-west1185 ms17.9 s2.7 s
us-east1271 ms14.7 s2.7 s
asia-south1596 ms22.0 s3.6 s

The cost: the first answer takes 17–71 s, against 16–33 s for stock anon-rpc, because Atmos proves a route, and verifies the chain head, before it answers.

Medians of 4 sessions each, Cloud Run, 2026-11-06 · every session at atmos.xavio.dev/benchmarks

Privacy, honestly

Who, when, what

  • WhoHidden from the provider: it sees a mixnet exit.
  • WhenHidden for outgoing requests with opt-in shaping. Replies are not padded.
  • WhatNot yet: providers see which accounts you query. Access-list updates hide repeat reads (experimental).

Found upstream

What we found in anon-rpc itself

  • SecurityThe Node harness follows redirects past its own address policy, to loopback or cloud metadata
  • SecuritygetRandomValues above 64 KiB returns a partly zero buffer, silently
  • BugResponse.url is empty when the worker omits it, which breaks libraries such as Helios
  • ReportedA lying bootstrap RPC can choose which worker runs (told to the author privately)

Each fix is tested on upstream's own code: it fails before, passes after

Next

Roadmap

  • BuiltRouting, batching and failover · verified reads · the Node harness · hardening · the SDK and the host
  • Built, opt-inConstant-rate shaping · access-list updates (experimental)
  • NextProvider splitting, so no single provider sees every address
  • PlannedA Nym transport fork: warm connections per provider, safe retries, HTTP/2

atmos.xavio.dev · github.com/xavio2495/Atmos-RPC