Your connection is exposing your IP and fingerprint.
We strongly recommend using Tor or enabling
Module · Mixer

Break the link, pool by pool.

Spend a private note through a batched zero-knowledge epoch. The link between sender and receiver is severed — no amount ever touches the chain in clear.

Epoch #42
Batched
5 notes in pool
1.7 ETH total
#00210.2 ETH
#00670.4 ETH
#01100.1 ETH
#01450.7 ETH
#01820.3 ETH
Per-user proof
mix_spend_air
Epoch proof
epoch_air
TEE
tfhe-rs
Amounts stay homomorphically encrypted — the chain sees only commitments and roots.
Checking local wallet…
Under the hood

The privacy pool, explained.

The mixer is the core privacy pool of Nox: per-user spend proofs, batched epoch proofs, and a TEE that never reveals amounts.

ZK epochs

Batched Plonky3 STARK proof (epoch_air) per asset, verifying conservation across the whole batch.

Per-user proofs

mix_spend_air proves ownership, Merkle membership, and computes the authorization commitment.

TEE coprocessor

tfhe-rs accumulates encrypted amounts homomorphically — no one outside the TEE ever sees individual amounts.

Opaque L1

lockPrivateIntent, finalizeEpoch, and settleEpochCommitments move only commitments and roots.

One epoch, four movements.

Mixing is not one transaction — it is a batched ceremony. Here is the sequence, in order.

1

Lock intents

Spenders submit lockPrivateIntent: their notes are pooled for the epoch. Only commitments appear on L1.

2

Prove per user

Each spender proves ownership and computes their authorization commitment with mix_spend_air.

3

Aggregate in TEE

The coprocessor sums amounts homomorphically — tfhe-rs adds ciphertexts without ever decrypting them.

4

Settle the batch

epoch_air verifies conservation for the whole batch; settleEpochCommitments mints change notes. Done.

Unlink yourself.

Pool funds with ZK proofs and vanish — change notes minted back as new private commitments.