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

The Atmos SDK

createAtmos() gives you an EIP-1193 provider for Sepolia. Every call leaves through the Nym mixnet, and reads are checked against a light-client head before they reach your code. It runs in the browser and in Node, and works with viem, ethers and wagmi.

Not on npm yet. The SDK is the sdk/ folder of the Atmos repository. Install its dependencies there (npm install in sdk/) and import sdk/index.js in the browser or sdk/node.js in Node. The Node runtime also needs the harness built: cd harness && npm install && npm run build.

Quick start

import { createAtmos } from "atmos-rpc"; // sdk/index.js in the browser, sdk/node.js in Node
import { createPublicClient, custom } from "viem";
import { sepolia } from "viem/chains";

const atmos = createAtmos();
const client = createPublicClient({ chain: sepolia, transport: custom(atmos) });

console.log(await client.getBalance({ address: "0x…" })); // proven against the verified head
atmos.close();

The first call waits for the provider to start: 15 to 70 seconds while the worker downloads, joins the mixnet, finds a route and verifies the chain head. await atmos.ready to wait for it explicitly.

Options

OptionDefaultWhat it doesWhat it costs
checkpointfinalized root two beacon APIs agree onthe light client’s trust anchor (a beacon block root)pass your own to avoid trusting the beacon APIs on first use
balfalsekeeps accounts you have read current from each block’s EIP-7928 access list, verified against the header, so reading them again names nothing to a providerone list per block (70–160 KB), on two extra mixnet routes of its own so the wallet’s calls never wait; about a minute to catch up after start. Experimental: it keeps pace with the chain in some sessions and not others. While it keeps pace, repeat reads name nothing; when it falls more than 2 blocks behind, reads fall back to proofs, which do name the account. status().following.behind shows which. Sepolia only
shapefalseevery call leaves on a fixed clock, padded, with dummies in the gapsabout one slot per call: up to 4 s for reads, 8 s for proofs
prefetchfalsere-proves recent reads at each new block and answers repeats at onceextra traffic on every block
lognonecalled with each internal event (checkpoint, route-accepted, …)

What is verified

MethodHow it is answered
eth_chainId, net_versionlocally
eth_blockNumberthe verified head, no request
eth_getBalance, eth_getTransactionCount, eth_getCode, eth_getStorageAteth_getProof checked against the head’s state root (or the access lists, with bal)
eth_callrun in a local EVM on proven state
eth_estimateGasthe provider’s figure, with the call proven not to revert
eth_getTransactionReceiptchecked against the block’s receipts root
eth_getBlockByNumber, eth_getBlockByHashheader proven; transaction list is the provider’s
eth_sendRawTransactionsent through the mixnet; the returned hash must match
anything elsesent through the mixnet unverified, and counted

atmos.status() returns the counts by kind (verified, advisory, plain, local, failed), and with bal how many accounts are kept current.

Sending transactions

Atmos holds no keys: eth_accounts is empty and eth_sendTransaction is refused. Sign with a local account and send the raw transaction:

import { createWalletClient, custom } from "viem";
import { privateKeyToAccount } from "viem/accounts";

const wallet = createWalletClient({ account: privateKeyToAccount(key), chain: sepolia, transport: custom(atmos) });
await wallet.sendTransaction({ to, value }); // signed here, broadcast over Nym

Events

The provider emits connect (with { chainId: "0xaa36a7" }) once ready, and disconnect if it fails to start or is closed. It never changes chain or accounts.

In a browser page

The worker runs in anon-rpc’s sandboxed iframe harness. A Content-Security-Policy on your page applies to it too; it needs script-src 'unsafe-inline' 'wasm-unsafe-eval' blob:, worker-src blob:, and connect-src for https://validator.nymtech.net, the worker’s download hosts (cdn.jsdelivr.net, unpkg.com, raw.githubusercontent.com) and wss: for the gateways. The demo runs under exactly that policy.