A shielded pool breaks the link between your wallet and the trade. A Venice agent finds the route and keeps none of the conversation. Neither the model nor the chain learns who asked.
no accounts · no analytics · not audited
Two layers
Privacy on the chain and privacy in the model are different problems. ZKVENICE solves each with the tool built for it, and keeps them from ever meeting your wallet.
Layer 1 · the chain
Deposit with a commitment. Withdraw with a proof and a nullifier. Swap on the way out, to an address that never deposited. The link is not hidden; it is never written.
Layer 2 · the model
The planning runs on Venice: open-weight models with no policy layer, zero data retention, three hundred models behind one key. It reads your intent, quotes the route, and forgets.
How a swap runs
The plan is made off chain and forgotten. The chain gets a deposit and, later, a withdrawal it cannot pair with it.
You type what you want in plain words. "0.4 ETH to USDG, best route, private." No form, no account.
A Venice agent quotes the route across Uniswap v3 and v4 pools on Robinhood Chain and writes the plan. Venice keeps none of it.
Your wallet deposits into the pool with a commitment. From here on, the chain has a deposit, not a person.
A proof of a valid note, with its nullifier, goes to a relayer. The relayer pays gas and cannot tell which deposit it is spending.
The pool swaps and sends the output to a fresh address. Two transactions, no line between them.
Why Venice
Any model can plan a swap. Only one provider is built so that planning it leaves nothing behind, and lets the agent pay for itself.
Venice does not persist prompts or responses. The conversation about your trade exists in your browser and nowhere else. TEE and end-to-end encrypted modes make that verifiable at the inference layer.
The open-weight models are served as they are. An agent running a five-step task does not get refused at step three for saying the word "private", and there is no review queue reading it.
Staked VVV mints DIEM: one token, one dollar of inference a day, in perpetuity. The agent holds it and spends it. There is no API key that resolves to you, and no invoice.
Read Venice’s own description of the agent surface at venice.ai/agents. ZKVENICE is a customer of that API, not a partner, and nothing here is endorsed by Venice.
What is real
A site about not lying to the chain should not lie to you. This table is the source of truth and it is updated before anything else on the page.
| Piece | State | What that means |
|---|---|---|
| Site and design | Built | What you are reading. Static, no analytics, no cookies. |
| Live quotes | Built | Prices read by your browser from DexScreener for chain 4663. Nothing is proxied. |
| ZK circuit | Built | Groth16, Poseidon, 20-level tree, 11,317 constraints. Proofs are made in the browser, never on a server. |
| Pool contracts | Live | Three pools on chain 4663 (0.01, 0.1, 1 ETH), bytecode read back and matched to the compiler. 26 tests on the real Uniswap v4 and v3 bytecode. Not audited. |
| Trusted setup | Dev only | One local contribution. Fine for testing, not for real money: a public ceremony comes before any launch. |
| Relayer | Off | The route exists; no relayer key is configured, so your own wallet submits the withdrawal and pays gas. |
| Agent on Venice | Built | The planner sends the sentence, and only the sentence, to Venice. Runs a local parser until a key is configured. |
| $ZKVENICE | Not launched | There is no contract address. Anyone giving you one is not us. |
Questions
It is a shielded pool with a swap on the way out. The privacy mechanism is the same family as any commitment-and-nullifier pool; the difference is that what leaves the pool is a different asset than what entered, sent to an address that never touched the deposit.
The text of your intent and the quotes it fetches, for the seconds it takes to answer. Venice does not store prompts or responses on its servers, and the open-weight models it serves have no policy layer that would refuse a swap or log it for review. Your wallet address is never in the prompt.
A deposit from your wallet into the pool, and later a withdrawal-and-swap submitted by a relayer to some address. Nothing on chain says the two belong together. Amounts use fixed denominations so size does not give you away.
The agent holds DIEM, Venice’s tokenised daily inference allowance. One DIEM is a dollar of inference every day, forever. The agent pays for its own thinking; there is no API key tied to you.
The pools are on chain 4663 at three denominations, and the app deposits, proves and withdraws against them. The relayer is off for now, so withdrawals are submitted by your own wallet. There is no token and no audit, and the trusted setup is a development ceremony. The status block above says exactly which is which.
The app is open
Live prices, the agent's plan, a Groth16 proof made in your tab, and three pools on chain to deposit into and leave from.
Open the app
