The Veil protocol

Privacy belongs onchain.

Veil is a privacy protocol for onchain finance. Its first application is a memecoin launchpad, presented here as a demo.

Explore the markets

One protocol, one identity. Pay, Swap, Bridge and Perps are future directions, not live products. The lifecycle, verification and privacy boundaries below describe the current launchpad protocol design—not guarantees for future applications.

Who sees what

Public

  • Prices and aggregate volume
  • Curve progress and graduation
  • Batch results and settlement proofs
  • Public liquidity and fees

Private

Not published with your identity.

  • Individual buys and sells
  • Trade amounts and price limits
  • Shielded balances and positions
  • Your personal P&L

Operator can see

Accepted intents, including amounts and limits. Actions can be linked within the same wallet and domain.

There is no public, wallet-linked trade tape. Privacy is against public observers, not the Operator, and depends on the batch anonymity set.

A familiar launch.
A different settlement.

Choose a quote asset. Example

A market belongs to one fixed Quote Domain. Balances do not move between Quote Domains, and changing this example does not switch your wallet.

Quote Token

Example market · COIN / USDC

Illustrative only. Live assets and availability require a verified deployment.

  1. Launch on a shared set of rules.

    Create a token on a fixed bonding curve. No creator allocation or custom trading rules. Buying opens in the next full slot after creation settles.

  2. Trade in uniform-price batches.

    Choose an amount and price protection. Accepted intents are grouped for settlement. Executed trades in the same market batch share a clearing price, with applicable fees. Partial fills are possible; submission does not guarantee a fill.

  3. Graduate into Uniswap v4.

    When the curve reaches its reserve target, graduation happens atomically in the final curve batch. Trading continues through Veil’s gated v4 pool; third-party liquidity positions are public.

Private inputs.
Provable rules.

Every private state transition requires a valid ZK proof and the current Operator’s result signature. Balances, market state and real asset movements settle together—or the entire settlement reverts.

Your wallet signs locally, then recovers and verifies its own encrypted result. A settled batch alone is not proof that your order filled. The public Explorer shows batch-level facts, not your private history.

Explore demo batches

What privacy does—and does not—mean.

Not hidden from the Operator
The Operator sees accepted intents, including amounts and limits, and can link actions within the same wallet and domain. It can delay, censor or under-fill orders. Veil is not MEV-free.
Not immune to inference
Single-order or low-volume batches can reveal more through public aggregates. Deposits and withdrawals expose assets, amounts and public addresses; they are not unlinkable.
Availability is a real dependency
Before graduation, base tokens cannot be deposited or withdrawn. If the Operator stops and governance cannot restore service, these assets may remain indefinitely inaccessible. Quote and graduated base notes have a public full-note exit path, which exposes the note’s history.
Local keys still need a trusted client
Local signing depends on the browser and the code it runs. Keep an encrypted wallet backup; connecting the same external wallet cannot recover a lost Veil secret.