Supported wallets
Which wallets can use ZeroTrace - any wallet that signs deterministically with an ordinary key - and which cannot.
ZeroTrace works with wallets that sign with an externally owned account (EOA): an ordinary secp256k1 private key. Your wallet signs two things:
- the activation message, once per session, from which the app derives your privacy keys;
- an EIP-712 Spend message for every private send, sale and unshield. The zero-knowledge circuit checks that signature against the wallet key bound to your registered owner key.
Supported
| Wallet | Why it works |
|---|---|
| Browser and phone wallets with an ordinary key, such as MetaMask | They sign with an EOA key |
| Hardware wallets that sign EIP-712 typed data | Each Spend is a standard typed-data signature, confirmed on the device |
| EIP-7702 accounts | An EOA with a delegation still signs with its own key, so it can own notes like any EOA |
| MPC multisig wallets (Fireblocks, Copper, Lit and similar) | Several parties approve, and the result is one ordinary ECDSA signature |
The app connects to the wallet injected in the browser, or to any wallet app that supports WalletConnect: scan the code on a computer, or open the wallet from the list on a phone. The QR code is drawn by the app itself; the only WalletConnect servers it talks to are the relay, an encrypted channel to your wallet, and the check that tells your wallet the request comes from zerotrace.so. Your wallet must sign deterministically, as almost all do: the app checks it on first use (see Get started).
Not supported
| Wallet | Why not |
|---|---|
| Contract-based multisig wallets | The circuit checks one EOA signature, and the vault accepts a single verifier. A contract wallet has no key that can produce it. |
| Smart-contract accounts (ERC-4337 wallets and similar) | Same reason. At activation the app checks that the signature comes from the connected address, and refuses it otherwise. |
Any wallet, including a contract wallet, can still hold, send and trade public ZERO, since ZERO is an ordinary ERC-20. That balance is public and does not earn from harvests.
Deterministic signatures
Your privacy keys are derived from the activation signature, so the wallet must give the same signature for the same message every time. Wallets that follow RFC 6979, as most do, sign deterministically.
- The first time, the app asks for the signature twice and compares the two. If they differ, it refuses the wallet: "This wallet does not sign deterministically: your keys could not be recovered later. Use another wallet." Nothing is registered.
- On later visits, the app checks that the signature gives the key already registered for your address. If it does not, it stops with an error instead of showing a wrong, empty balance.
There is no other way to derive the keys, such as a passkey or a separate seed phrase.
Your notes depend on your wallet's key. If you move to a new wallet app, import the same key or seed phrase: a different key gives different privacy keys, and your notes stay with the old one. To move funds to a new key, send them privately to an address registered with the new wallet.
Changing devices
Nothing needs to be backed up or exported. Install your wallet on the new device with the same seed phrase, connect, and sign the activation message. The same key gives the same signature and the same privacy keys, and the app finds your notes on the chain.
Fees
The Pons trading fee, how the ZeroTrace harvester splits it between the team and private holders, the network fee of private transactions, and what you pay with your own ETH.
Staying private
Practical habits that keep your ZeroTrace activity private, and the limits the protocol cannot remove for you.