Get started
Atmos sends your Ethereum RPC calls through the Nym mixnet, from anon-rpc's sandboxed worker, and checks the answers against a light client before you see them. Use it from a wallet through a local host, or from your own app through the SDK. Sepolia only, for now.
In a wallet, such as MetaMask
Run the Atmos host on your own machine. It gives the wallet an ordinary RPC URL and sends every call on through Nym, checked against a light client.
curl -fsSL https://atmos.xavio.dev/install.sh | sh Then add http://127.0.0.1:8545/11155111 to MetaMask as a Sepolia network. Install has the requirements, the settings and how to remove it.
In your own app
The SDK’s createAtmos() returns an EIP-1193 provider, so viem, ethers and wagmi use it unchanged, in the browser and in Node.
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 SDK is not on npm yet: it is the sdk/ folder of the Atmos repository. The SDK docs cover its options, what is verified and what each option costs. The demo runs it in your browser.
What to expect
- The first answer is slow. It takes 15 to 70 seconds while the worker downloads, joins the mixnet, finds a working route and verifies the chain head.
- After that, a call takes about 0.5–0.6 s longer than plain RPC, which is the mixnet’s round trip. A verified balance adds about another 0.5–0.9 s for its proof, and the latest block number is answered from the verified head with no request. The benchmarks have the measurements.
- Providers see a Nym exit, not your IP. They still see what you ask for, including the addresses you read.
Underneath
Both run on client/atmos.js, the routing layer: batching, a standby route and failover, without verification. The Client API documents it for code that wants that layer on its own.