Docs · 04
How it works
Four steps: shield, screen, prove, route. What happens on chain, and what stays with you.
Nuluvium runs on Robinhood Chain testnet with test tokens. Nothing here is investment advice.
01Shield
Your deposit goes into the shielded pool, a fork of Privacy Pools v1.3.0 whose contracts and circuits are deployed unchanged. The pool records a commitment, a hash that hides who can spend it. The secret behind it, your note, stays on your device and can always be rebuilt from the chain with your keys.
02Screen
The approved-set provider checks every deposit: the OFAC sanctions list, the stock token issuer's blocklist, Nuluvium's own denylist, and the deposit caps. It publishes the list of approved deposits under its content hash and posts the list's root on chain. If a check cannot run, the deposit is not approved.
03Prove
For every piece, your browser makes a zero-knowledge proof: that you own an approved deposit with enough left, without saying which one. What is left becomes a new note that only you can spend. Proofs take a few seconds in the browser.
04Route
The relayer sends the proof to the Nuluvium Router in one transaction. The pool releases the piece's USDG, the Router swaps it on a public Uniswap v3 pool, and the stock tokens go straight to the fresh address. The order is signed by the fresh address, so the relayer cannot change it. The relayer pays the gas and takes its fee in USDG.
05What a reader of the chain sees
- A deposit into the pool from your wallet.
- Swaps from many fresh addresses, all sent by the same relayer, at different times and sizes.
- Not which deposit paid for which swap, and not that the swaps belong to one order.
06What stays on your device
Your keys, your notes, the fresh addresses and the order schedule. To find your notes, the app reads every pool event and picks out yours in the browser, so the services it calls do not learn which deposits are yours. The relayer sees one piece at a time, with no link to the others; its logs are off.
