Your connection is exposing your IP and fingerprint.
We strongly recommend using Tor or enabling
About Nox

Privacy without the "suspicious" label.

A financial system where legitimate users can be private — where privacy doesn't have to mean suspicious, and compliance doesn't have to mean surveillance.

Vision & mission

Amounts stay encrypted. Provenance stays auditable.

Entry stays gated. That is the technical posture Nox is built toward.

Make privacy operational

Notes that are actually private — ZK + TEE FHE — not just harder to read. Plaintext amounts exist only inside the enclave.

Make compliance structural

Screening, statuses, and holding periods enforced by contracts and canisters — not by a Terms of Service page.

Keep it decentralized

ICP canisters as the coordination brain, Ethereum as the settlement layer, no proprietary backend.

Be honest about limits

A documented threat model, a documented un-audited status, documented MVP paths. The docs are written from code.

Where we are now

The real state, not the marketing state.

Honesty about the current state is part of the protocol's security model.

ZK circuits (note, spend, mix, epoch)
Implemented + tested in-repo
TEE FHE batch mixing
Implemented (HTTP service, tfhe-rs)
L1 contracts
Implemented + Foundry tests
Canisters (relayer / verifier / indexer)
Deployed locally (dfx)
Withdraw
Clear-model MVP
External audits
None yet
Mainnet production
Not yet — waiting on audits

The team

No public roster — the code is the record.

The project is maintained by the contributors to the repository. No token, no governance, no formal DAO exists — decisions today are made by the maintainers and are expected to evolve as the protocol matures.

Plonky3 circuitsTEE / FHEL1 contractsICP canistersScannerFrontendDocs from code

Built in the open.

One repository, docs written from code, limitations documented on purpose.