Privacy belongs onchain.

A privacy protocol for onchain finance.

Explore apps How Veil works

Private inputs.
Provable rules.

These foundations describe Veil’s current Launchpad protocol design.

Private balances

Market data shows aggregate results, not a public wallet-linked trade tape. Shielded balances are not published.

Proof-checked settlement

A ZK proof and the Operator’s result signature are both required. State updates and asset movements settle together—or revert together.

Proofs do not guarantee inclusion or a fill.

Local verification

Your wallet signs locally, then decrypts and checks its result against onchain records. Root secrets and spend private keys stay on your device.

Local signing still depends on the browser and code you use.

Who sees what
Market data
Prices, aggregate volume and curve progress.
Settlement
Batch proofs and aggregate results.
Public flows
Deposits, withdrawals and public liquidity.
Accepted intents
Trade direction, amounts, limits and note openings.
Wallet linkage
Actions can be linked within the same wallet and domain.
Root secrets
Wallet root secrets and spend private keys are not shared.
Signing keys
Kept inside your local wallet.
Private results
Your fills, fees and shielded balances.
Verification
Decrypted results checked against onchain records.

The Operator sees accepted intents. Small batches can expose individual activity through inference; deposits and withdrawals are public.

Protocol details

Applications