Proofs on testnet

Ckb-Mixer

  • Testnet
  • Apps
  • DeFi
  • Protocol

A Tornado Cash-style mixer on CKB where deposits leave a note and withdrawals need only a zero-knowledge proof, no signature.

ckb-mixer.nervosscan.com · Listed 2026-11-20

Report a problem with Ckb-Mixer

No account needed. Reports are posted publicly on GitHub, so leave out personal details.

What is wrong?

Runs on CKB testnet only. Get test CKB from the faucet. Never send real assets to it.

About

What it proves

A Tornado Cash-style anonymity pool fits inside CKB's cycle budget. Each withdrawal verifies a Groth16/BN254 proof plus a 256-level nullifier set in about 69.4M cycles locally (about 2% of a block's 3.5G limit), and about 102.5M cycles for the smaller size build actually deployed on the public testnet. The pool keeps no Merkle tree on-chain: its entire state is 1,640 bytes in one cell. A withdrawal transaction has a single input, the pool cell, and no signature; the circuit binds the recipient and fee, so nobody can front-run a proof and change where the money goes. Pool v2 adds deposit-intent cells and batch settlement behind a Type ID: a depositor can leave after funding an intent, and anyone can bundle intents and withdrawals into one transaction. On testnet the largest batch settled 20 withdrawals in 2.05 billion cycles (59% of the block limit).

How it uses CKB

One pool is one cell that is never destroyed: a pool type script holds a depth-20 Poseidon commitment tree as 30 recent roots plus a frontier, and a sparse Merkle tree root for spent nullifiers, while a keyless pool lock means nobody can freeze the pool. The on-chain scripts are written in Rust for CKB-VM and share their core logic with the prover through no_std crates. The web demo connects a wallet with the official CCC connector, generates note secrets and withdrawal proofs in the browser via WebAssembly built from the same crates, and talks directly to a public testnet node with no backend of its own. A Cloudflare Worker acts as the aggregator, batching intents and withdrawals and paying the miner fee; if it ignores you, a self-send fallback broadcasts a signature-free single withdrawal. Both the page and the worker replay every pool transaction from the creation transaction and refuse to work unless the result matches the on-chain cell byte for byte.

Before mainnet

It runs on CKB testnet only, and the repository has no license yet (the README calls it internal research). The Groth16 trusted setup is dev-only, generated by one person with the toxic waste still on that machine, so a real deployment needs an MPC ceremony or a universal setup; the groth16-ckb verifier and the contracts are unaudited. The circuit binds only 31 of the 32 bytes of the recipient lock hash, there is no domain separation, and v1 pools have no Type ID, so lookalike pools with smaller anonymity sets are possible (v2 fixes this). Deployment locks 141k–297k CKB of capacity for the scripts and verification key, shared by all pools, plus 1,819 CKB per pool. The aggregator is a single-machine demo with no relayer guarantees, and the root history covers only 30 deposit transactions in v1.

Activity

ActiveLast activity 2026-11-19

Public GitHub activity in the last 30 days.

Activity per day, last 30 days

View as table
DayEvents
29 days ago0
28 days ago0
27 days ago0
26 days ago0
25 days ago0
24 days ago0
23 days ago0
22 days ago0
21 days ago0
20 days ago0
19 days ago0
18 days ago0
17 days ago0
16 days ago0
15 days ago0
14 days ago0
13 days ago0
12 days ago0
11 days ago0
10 days ago0
9 days ago0
8 days ago0
7 days ago0
6 days ago0
5 days ago0
4 days ago0
3 days ago0
2 days ago8
1 day ago3
Today0
Events, 30 days
11
People active, 30 days
1
GitHub stars
0

github.com/tianlitao/ckb-mixer · Public GitHub activity via CKB Pulse, updated 2026-11-20.

Projects that build in private repositories can look quiet here.

Build on it

Other proofs