Nox

Privacy at the network layer. Nox keeps who you are apart from what you send and how you pay, so each node, RPC provider and website sees only its own slice.

What Nox Does01
01

Hides Your IP

Your IP stops at the entry node.

Every packet is onion-encrypted and routed through three nodes: entry, mix and exit. Each hop strips a layer, waits a random delay and forwards a packet that looks like every other. Each node sees only its neighbours on the path.

02

Pays privately

Cover gas without revealing who you are.

A zero-knowledge proof shows you can pay without exposing your identity or what you’re paying for. Relay fees flow through a shielded pool with no on-chain link to you.

03

Routes You Securely

Every request mixed before it hits the network.

Transactions, RPC calls, queries. Everything passes through the mixnet. Services reply via anonymous return headers. They never learn your address.

Network →02
How Mixing Works

Continuous
Poisson Mixing

Each hop holds every packet for a fresh random delay, so arrival order does not set departure order. Between nodes, real packets, loop probes and drop cover share one fixed 32 KB format.

Use Cases03
Primary Application

Private DeFi on Ethereum

Integrates with the Hisoka darkpool. Your client builds a ZK proof locally, Nox routes it through the mix network, and the exit node submits it to Ethereum. You never touch the chain directly.

How it works
State modelZK-UTXO Merkle tree (depth 32)
OperationsDeposit, withdraw, transfer, swap
Gas paymentZK proof, payer identity hidden
DeFi accessAdaptor contracts (e.g. Uniswap V3)
ExecutionAtomic verify + execute on-chain
Web3 Privacy

Query the chain without revealing yourself

Every RPC call exposes what you're looking at and where you're calling from. Nox routes queries through the mix network. The provider sees the exit node, never you.

What you can read privately
Account balancesAny address, any token
Contract stateStorage slots, view functions
Event logsHistorical and streaming
CostFree. Reads don't require payment
Infrastructure

Private by default at the wallet layer

Nox sits below the wallet. Every interaction is mixed before it reaches a node or relay. Integrate with the SDK, or load the Nox worker for the anon-rpc standard in a browser wallet: it runs TLS with the RPC provider itself, so calls stay encrypted end to end. The RPC provider sees only the exit node's address.

Integration surface
RPC routingAll calls through mix network
Tx broadcastExit node submits, wallet hidden
Provider visibilitySees exit node, never the user
Integration methodSDK or anon-rpc worker, same wallet UX
Browser walletsanon-rpc worker 0.4.1
Wallet to providerEnd-to-end TLS
Worker specifier0x3513…7A9A, Sepolia
Session correlationFresh exit per request
Network →04
Role-based routing

Three hops per path: entry, mix, exit

Clients build Sphinx packets locally and route through entry, mix and exit hops. Node discovery uses an on-chain registry where nodes publish their public keys. Operators join by staking, and onboarding is open: the 10 live testnet nodes are run by Hisoka, and outside operators can register through the public operator kit. Every client derives the same topology from the on-chain registry; strict per-layer roles are the next milestone.

Private by design.
Open source.
Live on testnet.

Read Paper Launch Demo