VeilVeilmainnetOpen app →
Veil documentation

A privacy layer for everything you do on Solana

Veil gives your wallet a private balance. Shield any token into it, then send, trade, lend and withdraw without the chain linking any of it back to you. Your keys never leave your browser.

0.3%to shield
0%Veil fee on private transfers
0.3%to withdraw
—notes in the pool
Audited. Veil's on-chain program was audited by ContractWolf (98/100). After the audit the launch's deposit limits were lifted: no token has a per-deposit limit or a vault cap. A vault opened later for a new token starts with default limits until the multisig lifts them. See Security.

How it works

Value enters through a public shield, lives as sealed notes, and leaves through a public exit. Everything in between is proven, not revealed. Tap a stage.

Visible on Solana

Phantom, Solflare or Backpack stays your public identity. It signs exactly one thing in Veil: a shield. Veil never holds or sees its private key.

The three pieces

Notes

Each note commits to a token, an amount and its owner. Only your viewing key can open it; only your spending key can spend it.

Proofs

Groth16 zero-knowledge proofs, built in your browser, convince the Veil program that balances add up and you own what you spend.

Relayers

A relayer submits your proof and pays the network fee. It can't change where funds go: the recipient and its fee are bound into the proof.

Quick start

Connect your walletPhantom, Solflare or Backpack. It stays your public entry and exit.
Create your vault and save the recovery keyA random key generated in your browser, encrypted with your passphrase. Write the recovery key down: it is the only way back if this browser is lost.
Shield a tokenOne wallet signature moves it behind the privacy wall.
Use it privatelySend to a veil2… address, trade, or lend. No wallet signatures, no public link.
WithdrawTo any address, by default a fresh one-time address only your vault controls.

Shield

Moves any registered SPL or Token-2022 token from your wallet into Veil. SOL is wrapped and unwrapped automatically. Your wallet pays the amount plus the 0.3% Veil fee and signs once; the note is sealed in your browser.

Any token can get a Veil vault: if it doesn't have one yet, anyone can open it for about 0.004 SOL of rent. Tokens with features that could put a shared vault at risk (permanent delegates, transfer hooks, pausable mints) are refused on-chain.

Tokens with their own rules (Token-2022)

Transfer fee. Some tokens take their own cut of every transfer, set by their issuer (for example 3%). Shielding sends that fee on top: your wallet pays the amount, the Veil fee and the token's fee, and MAX works all three out to the unit. Withdrawals arrive less the token's fee, and the review shows exactly what lands. A private send moves nothing on-chain, so the token charges nothing there. The fee goes to the token's issuer, never to Veil.

Holder rewards (scaled or interest-bearing balances). Some tokens grow every holder's balance through an on-chain multiplier. Veil shows your private balance, its dollar value and every amount the way your wallet would (the raw amount times the token's current multiplier, read from the chain every minute) with a small “Includes holder rewards” note. What moves on-chain is always the raw amount, so nothing is lost or created by the display.

Crowd size matters. A token few people use is easier to trace from entry to exit. The app shows each token's crowd and warns when it's small.

Send privately

Pay any Veil address (veil2…; its last characters are a checksum, so a typo is caught) in any token. There's no wallet signature and no Veil fee, only the relayer's network fee. When you hold private SOL, Veil pays that fee in SOL, and the transaction doesn't name the token you sent.

The recipient's app finds the payment by trying to open every new note with its viewing key, so nobody (not even the indexer) learns which notes are whose.

Usernames

An @username is a public, opt-in name for your Veil address: people can pay @alice instead of a long veil2… address. It is claimed from the top of the Wallets list in the Chrome extension and the phone app, and anyone can pay one from Send, on the website too.

ClaimPick a free name in Wallets: your device signs a record “@name pays this address” with that address’s names key
StoreVeil’s indexer checks the signature and the rules, and keeps the record; it can’t change it without the signature failing
CheckA sender’s app fetches the record and verifies it against the address itself, then shows the name, avatar and address
PayAn ordinary private transfer to that address: on-chain it looks like any other
Names taken—Live @usernames in the registry
New this week—Claimed in the last 7 days
Cost to claimFreeA short proof of work in your browser
Loading live numbers…Veil indexer · public name registry

Rules

  • 3–20 characters: a–z, 0–9 and _. Case doesn’t matter: @Alice is @alice.
  • First come, first served. One live name per address.
  • Names that could pass for Veil or its team are refused: veil, admin, support, team, official and similar, including look-alikes such as ve1l or adm1n.
  • Free to claim. Each change carries a short proof of work made in your browser, and the registry takes a limited number of changes per hour for everyone together, like the bug bounty form.
  • It pays one wallet’s private address: Wallet 1 unless you choose another. Switching is signed by both wallets.
  • Release it any time. It then rests for 30 days, when only you can take it back; after that anyone may claim it.

How a name is checked

Each record (“@alice pays veil2…, avatar, sequence number, time”) is signed by a names key: a key derived from the address’s viewing key for names only, by multiplicative key blinding as Tor’s onion services do. Its public half is computed from the address alone, so every app checks the signature against the address it is about to pay, and refuses on any mismatch. Veil’s indexer stores and serves the records (POST /v1/names, GET /v1/names/:name); it can’t alter one, and it refuses moves not signed by the address being left. Nothing about names touches the circuits, notes or proofs.

A signature can’t stop one thing: an indexer answering a name nobody on your device has paid before with a whole other record that is itself validly signed. So your app pins the address it first saw for each name and warns you if a later answer differs without the owner’s signed move; Send always shows the address before you confirm (compare it with the person the first time); and a Receive QR carries the address itself, cross-checked against the registry.

Receive QR

With a name, the QR on Receive holds veil:@alice?to=veil2…. Scanned with Send → Scan in Veil, it opens Send with both filled in; the app checks them against each other, and if the registry can’t be reached it uses the address from the code, and says so.

Avatars and your photo

Pick one of Veil’s preset avatars, an emoji on a colour, or your own photo. A photo is cropped and compressed on your device to a 128 × 128 WebP of at most 10 KB and kept in your encrypted wallet. It is never public: everyone else sees your monogram instead. With profile sync on, it travels to your other devices only inside your encrypted profile (below). In the extension you pick it with a file picker; on iPhone the system photo picker opens, with no Photos permission.

Profile sync

Your @username link, avatars (the photo included) and wallet names follow your wallet to the website, the extension and the phone app, and come back with your recovery key. The profile is encrypted on your device (AES-256-GCM) with a key derived from Wallet 1’s recovery key, domain-separated (veil/profile/v1), and stored on Veil’s indexer under an id that is a hash of a signing key derived the same way: never your address. Every write is signed by that key, so only you can replace or delete it; the newest version wins, and two devices’ changes merge field by field, the newest of each. The indexer only ever holds ciphertext. Turn it off, or delete the stored copy, in Settings → Privacy (Keys & backup).

What is public: your @username, the address it pays, your preset or emoji avatar, and when you claimed or changed it. That shows you use Veil. What stays private: your balance, your activity, who pays you and how much (a payment to @alice is an ordinary private transfer), your wallet address, and your photo. The indexer sees which name is looked up, never who looks it up.

Trade

Swap inside your private balance through Jupiter. On-chain, Veil's vault is the trader. You set a minimum output; if the market can't meet it, nothing is traded and your input returns to your private balance automatically.

Each trade runs in two steps: your proof sets aside the input in an escrow of its own, then the route runs. The program checks the escrow paid out exactly the input and the vault received at least the minimum you approved. The quote and that minimum come from the relayer, so the app compares them with the market price before you approve.

Earn

Lend from your private balance through Jupiter Lend. Your position is a private note of the market's share token (for example jlUSDC), and it grows as the share price rises with interest. Withdraw turns it back into the underlying token, privately.

Lending has its own risks: smart contracts, borrowers, and withdrawal limits when a market is busy. Veil hides who lends; it doesn't insure the market.

Withdraw & one-time addresses

Withdraw sends funds to any Solana address. By default it creates a one-time address derived from your vault, so nothing ties it to your wallet. Your recovery key restores every one of them.

Receive works the other way: give a payer a one-time address instead of your wallet. When funds land, shield them back with one tap. It's gasless: the relayer pays the network fee and takes its fee from the deposit, so even a token-only address works.

Add funds & Recover funds

The Veil Wallet (the extension, the phone app, or the wallet Veil makes on the website) has an Add funds address: a Solana address derived from your vault's root (index 700,000), so your recovery key restores it. Send SOL or any token to it from an exchange or another wallet. While Veil is open and unlocked, whatever lands there is shielded into your private balance by itself, gasless: the relayer pays the network fee and takes its fee from the amount.

How much is shielded

Always the raw on-chain amount in the address's associated token account, the one the deposit debits. A deposit of amount debits the Veil fee (0.3%, none with Veil Pro) on top, and for a Token-2022 token with a transfer fee, the program grosses that up again so the vault receives the whole of it (gross_for_net, Token-2022's own inverse-fee rule at the current epoch; less arriving fails with DepositShortfall). The app works out the largest amount whose debit fits the balance, to the unit, so a 3% fee token shields about 3% less than it holds, not nothing. Display-only extensions (scaled UI amount, interest-bearing) never change the raw amount.

When it can't move in

Some things a retry can't fix: a token with no Veil vault yet, a token frozen by its issuer, a deposit above a token's limits, a disabled token. These are shown once, in words, and not retried until the balance there changes. A busy network is retried a few times, then left too. Nothing is ever sent when a shield fails.

Recover funds

Any arrival that hasn't moved in has a Recover funds button, and so does every balance under Keys & backup → Add funds address. It sends all of that token back out, to the wallet it came from (read from the account's recent transfers, through Veil's own RPC) or an address you type, then closes the emptied token account. One transaction:

  1. Compute budget: 60,000 units.
  2. Open the recipient's token account if it has none (associated token account, idempotent).
  3. Token-2022 only, if the account holds withheld transfer fees: harvest them to the token's mint (a token account can't close while holding them; anyone may do this).
  4. TransferChecked of the entire balance, signed by the Add funds address.
  5. CloseAccount: the account's rent (about 0.002 SOL) goes to your connected wallet.

No Veil fee. On the website your connected wallet pays the network fee (about 0.00001 SOL, plus about 0.002 SOL of rent if the recipient has no account for the token). In the extension and the app, Veil's relayer pays it (POST /v1/sponsor-recover), for this exact transaction shape only: exactly two signers, no lookup tables, the transfer moves the account's entire balance as the chain holds it, the account closes, the relayer appears only as fee payer, account funder or rent recipient, and a simulation must show it pays no more than the network fee. If the relayer opens the recipient's account, the closed account's rent repays it. Each client gets at most 5 an hour, within an hourly budget for everyone.

A transfer-fee token still takes its own fee on the way out (to its issuer, not Veil): the review shows what arrives. Everything is shown in full before you confirm, and a recover is rebuilt and checked against what you saw just before it is signed.

Public, like any transfer. The chain sees the Add funds address send to the recipient. If the tokens came from an exchange, its deposit address may not credit a return: send them to a wallet of your own instead.
Season 1 · from 31 October 2026, 16:00 UTC

Veil Points

Keep value shielded in Veil and it earns 1 point per $1 per day, in every token with a price, $VEIL included. Each day of a season pays out part of a $VEIL pool to those points, and your holdings also collect their share of any holder rewards that land in Veil's vaults.

Season pool—$VEIL, paid out by the daily drip
Points this season—Counting starts with the season
$VEIL per 1,000 points—Estimate: paid so far ÷ points so far
Yearly yield, live—The last day’s drip, in dollars, × 365
Days left—Season 1 starts 31 Oct 2026, 16:00 UTC
Collect · redeemSoonCollecting opens soon
Loading live numbers…Veil program accounts · Veil indexer

How a day works

PriceRight after each daily boundary, every token is priced (Pyth, or the price keeper) and its points index rises by that price
Leafadvance_epoch appends one leaf: the day number, the note tree’s size and every token’s indexes
DripThe same call pays the day’s $VEIL: its budget, or less if the 50% yearly cap binds
ClaimYour notes’ share is worked out from the leaves; collecting and redeeming open with a later upgrade

Days (epochs) are 24 hours long, counted from 31 October 2026, 16:00 UTC (20:00 in Dubai), not from midnight: epoch k starts at the season start plus k days. Seasons last 90 epochs.

  • Earning. Each token has a public points index. Every day a token is priced, its index rises by that day's price per unit. A note holding amount earns amount × the rise while it sits in your private balance: 1 USDC held for one day at $1 is 1 point. No multiplier for anyone, Veil Pro included.
  • Which notes count. A note earns the rises after the first daily leaf that already includes it (its position in the note tree is below that leaf's tree size). A deposit made just before a day's pricing earns nothing of that day; the next day it does. Spending a note ends its earning, and the new notes it creates start their own.
  • Splitting changes nothing. Points, $VEIL and holder rewards are all linear in the amount: one note of 1,000 or ten of 100 earn exactly the same. There is no per-wallet limit (it couldn't be enforced privately, and splitting would beat it).
  • Holder rewards. Tokens that pay holders by sending more tokens to the vault (reflections) leave a surplus over what users own. That surplus is recorded each day in a reward index and credited pro rata to every note by amount × time, in the note's own token. User funds and protocol fees are never counted as surplus.

The daily drip and the 50% cap

Each season has a $VEIL pool (Season 1: 5,000,000 $VEIL, funded by the team; the year-1 budget is 20M). Every day pays at most its budget, pool × (d+1)/90 − pool × d/90 (the 90 days add up to the pool exactly), plus anything earlier days left unpaid. And it never pays more than a 50% yearly rate on the dollars shielded that day, in $VEIL at that day's price:

paid = min(budget + carry, day's points × 0.50 / 365 ÷ $VEIL price, what the pool vault holds beyond what it already owes)

What a day leaves unpaid carries to the next day, and at the end of the season into the next one. Every point of the day gets the same $VEIL rate, whatever token earned it. Two worked examples, at $0.0035 per $VEIL:

  • $1,000 shielded for 90 days, alone in the pool: the cap binds every day (about $1.37 of $VEIL a day), so it earns about 35,000 $VEIL, roughly 0.7% of the pool; the rest carries over.
  • $500,000 shielded: each day's budget (about 55,556 $VEIL, about $194) is all paid out, about 14% a year. More value shielded shares the same budget, so the yield falls as Veil grows.

The details

Epoch24 hours from 31 Oct 2026 16:00 UTC; one leaf per epoch, appended by advance_epoch from 10 minutes after the boundary (the first hour by the price keeper's crank, then by anyone). A missed day is paid by the next leaf; nothing is lost.
Season90 epochs. Pool and cap are set per season by the multisig, and only before the season starts.
PricesPyth where a verified feed exists for the token (owned by Pyth's receiver program, fully Wormhole-verified, the configured feed, fresh, published after the boundary). Every other token, $VEIL included, is priced once a day by a price keeper appointed by the Squads multisig. A price with confidence over 2% is never used (that token waits for a better one); a price is held within ⅓× to 3× of the token's 7-day average.
Your claimPoints: amount × rise of the points index. $VEIL: amount × rise of the token's VEIL index, which trails by one day (a day is paid at the rate of the leaf that closes it), so a note's $VEIL counts from the day after its first points day: a note never claims $VEIL for a day it earned no points. Holder rewards: amount × rise of the reward index.
Collect · redeemcollect_points and redeem_points exist but refuse until a second upgrade installs the collect circuit; collecting opens soon. Its trusted-setup ceremony (the Veil team's contributions on separate machines) is finalized with a public random beacon announced in advance: drand mainnet round 6615206, due 5 Nov 2026 at 14:00 UTC. Redeeming pays $VEIL 1:1 from the pool vault after the season, with no deadline.
FeesNone for earning. Pricing and appending leaves are paid by Veil's relayer (the crank).
Program instructionsprice_asset_pyth · price_asset_keeper · advance_epoch · init_season · set_season_params · collect_points · redeem_points
What the chain sees: each token's daily price and indexes, each day's leaf (the note tree's size and every token's indexes), each day's total points and $VEIL paid, and the pool. That is the same for everyone. What stays private: who holds what, how many points you have, and which notes are yours. Your app downloads the public list of leaves (GET /v1/points/epochs, the same for everyone) and works out your points on your device from your own notes: nothing about them is sent. Collecting will prove your points with a zero-knowledge proof, like any other Veil action.

On Home: the Points row and view

Under your private balance (on the website, in the extension and in the phone app) one slim row sums up your points: a status line, a detail line and one action. The action is the next thing you can do, in this order: Start, when nothing is shielded yet. Tap the row for the full view: a window over the wallet on the website, a full panel in the extension popup, a screen of its own on the phone. Back, a tap outside it, or Esc closes it.

  • You've earned. Everything your notes have earned this season, in $VEIL: your collected claim (your claim notes), what is still accruing on your notes (worked out from the public epoch list, exact when collected) and what was lost to spends before 6 Nov. Its dollar value is at the app's market price for $VEIL. A bar splits it into those three parts, each explained on hover or tap.
  • A live estimate. Between daily records the accruing points tick up at 1 point per $1 shielded per day, at today's prices, labelled as an estimate: the exact points are recorded at the next daily record (16:00 UTC, 20:00 Dubai), counted down beside it. With reduced motion the figure stays still.
  • History. Your collects, recoveries and redeems, from your vault's encrypted Activity, each with its transaction on Solscan.
  • What it reads. Your own notes, on your device, and the season and the program's flags from Veil's indexer (GET /v1/points and /v1/points/epochs, every minute while the app is in view). Nothing about your notes is sent.
  • Copy diagnostics. A link under the main button copies, as plain text, how your points are worked out: for each unspent note its token and amount, the daily record it entered after, and its points record by record, then the totals, your claim and what was lost to spends. Paste it into a support message if a figure looks wrong. It holds no keys, no addresses and no note positions or commitments (those would point at your transactions on chain); nothing is sent anywhere unless you paste it.
  • Anyone can check the season's arithmetic. GET /v1/points/reconcile re-derives every day from the program's own events, per day and per token: the day's points are the sum of every token's; budget = yesterday's carry + the pool's daily share; paid = the lesser of the budget and the season's cap (50% a year); q = paid × 1018 ÷ points; each token's index rise = price × 106 ÷ 10decimals per day; its $VEIL index rise = the previous rise × q ÷ 1012; and the season's paid and owed against its accounts. Any failure shows with the day and token.

Trust: the price keeper can't move funds. It sets the daily price of tokens without a Pyth feed, $VEIL included, held within ⅓× to 3× of each token's recent average: a dishonest keeper could still walk a price up by up to 3× a day over several days (more points for that token's holders; a lower $VEIL price makes each day pay closer to its budget), and a token's first price has no average to hold it. The drip never pays more than the day's budget. Every price it posts is public (AssetPriced events), and the multisig can replace it. The multisig can't change a past leaf or an index.

Invite & earn

Every vault can create an invite link. Friends who shield through it get 50% of Veil's shield fee back for their first 30 days, and you earn 20% of the shield fees they pay for 12 months. Open Invite in the app.

Create your linkIts code is a one-time address from your vault, never your wallet.
Share itveilit.xyz/r/<code> opens the app with your invite attached; it is remembered in your friend's browser.
Friends shieldEach of their shields carries a small public tag with your code. Only shields count: what happens after that is private, even from you.
Get paid weeklyEvery Monday the treasury pays your share to your invite address and their rebate to the wallet they shielded from. One tap moves yours into your private balance.
What is public. The tag links your invite address to your friend's shield, which is a public deposit anyway. Payouts are ordinary transfers from the treasury to your invite address. Neither touches your wallet or anything inside Veil.

What is public, what is private

Pick an action to see exactly what the chain records and what stays sealed.

What Solana sees
  • That a private transfer happened
  • The relayer fee (in SOL when you hold private SOL)
  • How many notes were spent (1–4)
What stays private
  • Sender
  • Recipient
  • Amount
  • Which token, when the fee is paid in SOL
With no private SOL, the relayer is paid in the token itself, so that transfer shows which token moved. The app tells you before you confirm.

Good habits

  • Don't withdraw the exact amount you shielded to the same wallet right away.
  • Keep a little private SOL so transfers can hide their token.
  • Prefer tokens with a big crowd; wait a while between shielding and withdrawing.
  • Reach the relayer through a network-level privacy tool if your IP address matters to you.

Fees

Veil's fee is 0.3% each time value crosses the privacy wall: when you shield, trade or withdraw. Private sends between Veil users have no Veil fee. The program enforces the rates; here they are, read live from the chain:

ActionVeil feeRelayer fee
Shield0.3%, on topNone (your wallet pays the network fee)
SendNoneNetwork fee + rent for each note spent
Trade / Earn0.3% of the inputNetwork fee + rent
Withdraw0.3% of what you withdrawNetwork fee + rent (+ opening the recipient's token account if needed)

100% of Veil's revenue goes back to $VEIL: it buys $VEIL on the market and burns it. See $VEIL token.

Try it

Action
Amount (any token)
Veil fee0.3% · 0.3
ResultYour wallet pays 100.3; 100 lands privately.
Official platform token

$VEIL token

$VEIL is the official token of the Veil platform. 100% of Veil's revenue buys $VEIL on the market and burns it, so the token grows with every private shield, trade and withdrawal.

Price—USD, live market price
Market cap · FDV—Price × total supply
Supply—Tokens in existence
Freeze authority—Read from the mint
Loading live numbers…Solana mainnet · Veil indexer
Official contract · Solana
HgTGdc29D5bDMrDvsCLnorxz899VyDj7ZN7FPa6vpump
Ticker$VEIL
NetworkSolana mainnet
StandardToken-2022
ExplorerView on Solscan

100% of revenue: buyback and burn

FeesShielding, trading and withdrawing each pay a small protocol fee
TreasuryCollected on-chain into Veil’s Squads multisig
Buyback100% buys $VEIL on the open market
BurnThose tokens are destroyed for good

100% of Veil’s revenue (all of its protocol fees on shielding, trading and withdrawing) is used to buy $VEIL on the open market and burn it. Burned tokens are gone for good, so every buyback permanently shrinks the supply. As more value moves through Veil, more $VEIL is bought back.

Every step is an ordinary on-chain transaction: the fees reach the treasury through the program’s collect_fees instruction, and the buybacks and burns appear on any Solana explorer. The numbers above are read live from the chain and Veil’s indexer.

Live buyback & burn. 100% of $VEIL’s pump.fun creator fees are used by the creator wallet (E2XHr7…CaLn) to buy $VEIL and burn it, and the buyback wallet (BdSCX5…fehu) buys $VEIL with platform fees each time it has collected $200 and burns it. Every buyback and burn, the total $VEIL burned and the SOL spent are on veilit.xyz/dashboard, live from the chain.

Getting $VEIL

Privately, in VeilOpen Trade and swap into $VEIL from your private balance. It lands in your private balance like any other token, and the chain never links it to your wallet.
Anywhere elseAny Solana exchange or wallet that trades it. Always check the contract address above: copies with the same name are not $VEIL. In the app, only the real $VEIL carries the lilac Official platform token check, because the app recognises it by its contract, never by its name.
Good to know. You don’t need $VEIL to use Veil: fees are paid in the token you move. Like any token, its price can fall as well as rise. Nothing here is financial advice. More answers in the FAQ.

Keys & recovery

Your vault holds one random 32-byte root. From it your browser derives a spending key (to spend notes), a viewing key (to find and open them) and every one-time address. It's encrypted with your passphrase (PBKDF2, 600,000 rounds → AES-GCM) and stored only in this browser.

  • The recovery key (shown once at creation) restores everything on any device. Anyone who has it can spend your private balance.
  • It is not derived from your wallet, so a wallet compromise doesn't expose your Veil balance, and vice versa.
  • Lose both this browser and the recovery key and the funds are unrecoverable. Nobody, including Veil, can restore them.

Security model

  • Non-custodial: only proofs from your keys move your notes. The admin can pause, set fees, caps and allowlisted programs, but cannot move anyone's funds.
  • Bound to the proof: recipient, fees and swap terms are hashed into the proof by the program itself; a relayer that changes anything gets an invalid proof.
  • Isolated swaps: each trade or lend has its own escrow and signer; an allowlisted protocol can only touch that one.
  • Multisig admin: a 2-of-2 multisig, handed over in two steps; it can pause, never move funds.

Testing, review status and live on-chain checks are on the Security page.

Bug bounty: up to $30,000. Find a bug that puts Veil's users at risk (moving or freezing funds, breaking privacy, or getting around a security check in the program, relayer, app or extension) and report it privately on veilit.xyz/bounty. Reports are encrypted in your browser to the Veil team's key before they're sent. Rewards, paid in USDC: Critical up to $30,000, High up to $10,000, Medium up to $3,000, Low up to $500.

Limits & risks

  • Anonymity set: privacy grows with the number of people using Veil, and per token for shields and exits.
  • Freezable tokens (like USDC) can have their vault frozen by the issuer. The app labels them.
  • Emergency pause: the multisig can pause deposits, transfers and swaps; withdrawals stay open. In an incident it can also pause everything leaving the pool for at most about 3 days (it ends by itself, and a new one can start only 7 days after the last).

SDK

@veil/sdk does everything the app does: keys, sync, proofs, and talking to the relayer. Proofs are generated client-side; nothing secret is ever sent.

import { VeilClient } from '@veil/sdk'
import { deriveKeys, rand } from '@veil/crypto'

const veil = new VeilClient({
  connection, programId,
  indexerUrl: 'https://indexer.example', relayerUrl: 'https://relayer.example',
  circuit: { wasm: '/circuits/transaction.wasm', zkey: '/circuits/transaction.zkey' }
})
veil.unlock(deriveKeys(rand(32)))   // keep the 32-byte root safe: it is the vault
await veil.sync()                      // download notes, find yours by trial decryption
console.log(veil.rootStatus)           // 'ok': checked against the program's own root on-chain

// tokens are named by mint (a token's own symbol is never trusted)
const SOL_MINT = 'So11111111111111111111111111111111111111112'
const USDC_MINT = 'EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v'
for (const m of [SOL_MINT, USDC_MINT]) await veil.resolveAsset(m)   // reads each token's Veil config from chain

Relayer & indexer API

Both are plain HTTP and keep no logs of who asked what. Anyone can run their own. Which addresses the app may connect to, checked live in your browser: API.

EndpointWhat it does
GET /v1/infoRelayer key, allowlisted swap and lending programs, protocol fee rates
GET /v1/fee?mint&inputsRelayer fee for a token and number of notes spent, and the account it's paid to
POST /v1/relaySubmit a proof (transfer, withdrawal, trade, lend); the relayer pays the network fee
POST /v1/sponsorGasless shield: co-sign a deposit as fee payer after a strict check
POST /v1/sponsor-recoverRecover funds from the extension or app: co-sign, as fee payer, a transfer of an Add funds balance back out and the close of its account, after a strict check
GET /v1/quoteSwap or lending quote, after the Veil fee
GET /v1/positionsLending markets, rates and share prices
GET /v1/commitmentsIndexer: every note commitment and ciphertext, in order (everyone downloads all)
GET /v1/nullifiers · /v1/rootIndexer: spent markers and the current Merkle root. With ?slots=1 (and &since= a slot): each spent marker with the slot it was spent in and whether a Veil Points collect spent it, the same list for everyone, so your app can work out on your device what your spent notes had earned
GET /v1/names · GET /v1/names/:nameIndexer: every live @username record (the same list for everyone), or one name with its signed history
POST /v1/namesIndexer: a signed @username record (claim, change, move, release) with its proof of work; checked, then stored
GET /v1/revenue/fees · /v1/revenue · /v1/burns · /v1/marketIndexer, public (veilit.xyz/dashboard): Veil's platform fees as DefiLlama reports them (per UTC day, last 24 hours, 7 and 30 days, all time; read by Veil's indexer every 10 minutes, so browsers never contact DefiLlama), which the dashboard shows, with the annualized pace (last 30 days × 365/30); creator fees and volume; every $VEIL buyback and burn of the buyback wallet; $VEIL's price and last 24 hours (Jupiter, read by the indexer) and its on-chain supply
GET /v1/revenue/daily · /v1/revenue/fees/compareIndexer, public: the indexer's own platform fees per UTC day (the program's ProtocolFee events at today's prices), and that figure against DefiLlama's for the last 7 full UTC days
GET /v1/points · GET /v1/points/epochsIndexer: Veil Points' season at a glance (pool, total points, $VEIL per 1,000 points, yield, days left), and every daily leaf with each token's indexes (the same list for everyone; your app works out your points from it)
GET /v1/points/reconcileIndexer: every day of the season re-derived from the program's events (AssetPriced, Dripped) and checked: day points, budget, carry, cap, q, each token's index and $VEIL-index rise and the shielded amount it counted, and the season's paid and owed against its accounts (ok, failures, per-day and per-token rows)

On-chain program

Program id · mainnet
FmsMbXrQXr1mARn45Cm52sdrwAWHDxqF8473t6woq9DP
InstructionPurpose
transactShield, private transfer or withdrawal, with a Groth16 proof (up to 4 notes in, 3 out)
swap_prepare · swap_execute · swap_refundTwo-step private trade or lending position through an allowlisted program
register_assetOpen a vault for a token (anyone; screened on-chain)
collect_feesSweep protocol fees to the treasury (anyone; treasury only)
set_* · accept_adminMultisig governance: fees, caps, pause, allowlist, two-step admin handover

Circuit: Transaction(26, 4, 3), Groth16 over BN254, 13 public inputs, verified with Solana's alt_bn128 syscalls. Notes live in a Poseidon Merkle tree of 226 leaves.

Questions & answers

FAQ

Everything people ask about using Veil and about $VEIL. Tap a question to open it.

Using Veil
What is Veil?

Veil gives you a private balance on Solana. Shield any supported token into it, then send, trade, earn and withdraw without linking any of it back to your public wallet. It runs on zero-knowledge proofs, so the chain checks every move without learning who made it.

How does Veil keep my activity private?

Your private balance is made of sealed notes. To spend one, your browser builds a proof that you own a valid note without saying which one. The relayer submits that proof for you, so your wallet never appears in the transaction, and observers only see that someone in the pool acted.

Does Veil ever hold my keys?

No. Your vault is generated and encrypted in your browser, and proofs are built there too. The relayer and indexer never get your keys. They see your IP address, and the relayer sees the transactions it submits for you, which are public on-chain anyway.

What is a @username?

A public, opt-in name for your Veil address, so people can pay @you instead of a long address. Claim one at the top of Wallets in the Chrome extension or the phone app: 3–20 characters (a–z, 0–9, _), first come, first served, free. It shows that you use Veil, never your balance or activity.

Can Veil redirect a payment to my @username?

Not without it showing. Your name’s record is signed by the address it pays, and every app checks that signature against the address before sending, so the indexer can’t change it. Apps also remember the address they first paid for a name and warn if it changes without your signed move, and Send always shows the address before you confirm.

Is my profile photo uploaded?

Never in a readable form, and never publicly. It is cropped and compressed on your device (128 × 128, at most 10 KB) and kept in your encrypted wallet. With profile sync on (the default), it reaches your other devices inside your encrypted profile, which Veil’s indexer stores but can’t read. Others see your preset avatar, emoji or monogram, never the photo.

Does my profile follow me to another device?

Yes, with profile sync on (Settings → Privacy, on by default): your @username, avatars, photo and wallet names come back on the website, the extension and the phone app, and after a restore with your recovery key. It is end-to-end encrypted; turn it off or delete it from the server there.

Can the Veil team freeze or take my funds?

No. The program has no path for anyone to move notes without the owner’s proof. The multisig can pause deposits, transfers and swaps in an emergency (withdrawals stay open), pause everything leaving the pool for at most about 3 days with 7 days between two such pauses, and set limits (disabling a token stops new deposits into it, never its withdrawals). It is also the upgrade authority, so it could change the program itself; upgrades are announced in advance.

Has Veil been audited?

Yes. ContractWolf audited Veil’s on-chain program and scored it 98/100, and every finding was resolved. The full report is public at contractwolf.io/projects/veil. Program upgrades need both signatures of a 2-of-2 Squads multisig.

Is there a bug bounty?

Yes. Find a bug that puts Veil’s users at risk and earn up to $30,000: Critical up to $30,000 (moving or freezing user funds, breaking privacy at scale), High up to $10,000, Medium up to $3,000, Low up to $500, paid in USDC. Report it privately at veilit.xyz/bounty, where it is encrypted in your browser to the Veil team’s key, then email the receipt to info@veilit.xyz with the subject “Bounty breach”.

What can I do with my private balance?

Hold it, send it privately to any Veil address, trade it into another token, earn yield through Jupiter Lend, and withdraw to any Solana address whenever you like. The chain never links any of it to your wallet.

What does it cost?

Shielding, trading and withdrawing each carry a small protocol fee, and private sends carry none. You see the exact amount before you confirm. Once your funds are shielded, the relayer pays the network fees for you. Current rates and a calculator are under Fees.

Is Veil anonymous?

Veil breaks the on-chain link between your wallet and your private activity. Your privacy grows with the crowd: the more people use a pool, the harder any one move is to trace. Your habits matter too (amounts, timing, tokens). No tool makes anyone 100% anonymous, and we won’t claim one does.

How do I get the most privacy?

Let some time pass between shielding and withdrawing, avoid unique amounts (round numbers blend in), withdraw to a fresh one-time address (the default), and keep a little private SOL so sends never have to name the token.

Something I sent to my Add funds address didn’t move in. What now?

Open Veil and unlock it: deposits move in while it is open. If one can’t (a token with no Veil vault yet, one frozen by its issuer, one above its limits), Veil says why once and stops retrying. Tap Recover funds on it, or under Keys & backup → Add funds address, to send all of it back to the wallet it came from or an address you choose. No Veil fee; the emptied account is closed and its rent returned.

What does “Includes holder rewards” mean?

The token grows every holder’s balance through a multiplier on its own contract (for example a rebasing or interest-bearing token). Veil shows your balance the way your wallet does, with the multiplier applied, so private balances grow with it too. Nothing extra is paid out by Veil.

Why was less shielded than I sent to Add funds?

Some Token-2022 tokens take their own transfer fee on every transfer, set by their issuer. It is taken once when the token reaches your address, and again when it moves into Veil’s vault, plus Veil’s shield fee and the relayer’s fee. The app works these out from the chain, to the unit, and shields the most that fits.

Which tokens work?

Any SPL or Token-2022 token without features that are unsafe in a shared vault. Anyone can open a vault for a new token right from the app.

Is there a browser extension?

Yes. Veil for Chrome is on the Chrome Web Store. It keeps your private balance one click away, holds several wallets under one password, and works alongside wallets like Phantom without getting in their way. Your recovery key works in the extension and on app.veilit.xyz alike.

What if the relayer goes down?

Your notes stay in the pool, untouched: try again when it is back. The relayer only submits proofs and pays network fees, and it can’t change what your proof allows. Anyone can run one, but each proof pays one specific relayer, and this app uses Veil’s.

I lost my recovery key and browser data.

Then nobody can recover the funds, because nobody else ever had your keys. Write your recovery key down when you create your vault and keep it offline and private.

How do I earn Veil Points?

Keep value in your private balance. From 31 October 2026, 16:00 UTC, every token with a price earns 1 point per $1 per day while it stays shielded, $VEIL included. Your points show on Home, worked out on your device from your own notes.

Does splitting my balance into many notes earn more points?

No. Points, the $VEIL drip and holder rewards are all proportional to the amount, so one note of 1,000 and ten of 100 earn the same. A newly created note starts earning from the next daily leaf.

My points look wrong. What should I send?

Open the Veil Points view (the Points row on Home) and press Copy diagnostics: it copies how each of your notes earned, record by record, with no keys, addresses or note positions. Paste it into your message to Veil. A note that arrived or was re-created (the change of a spend, a collect, a merge) starts earning from the record after next, which is the most common reason a day looks missing.

Can anyone see my points?

No. The chain shows each token’s daily price and indexes and the season’s totals, the same for everyone. Your app downloads that public list and works out your points from your own notes on your device; collecting will prove them with a zero-knowledge proof.

When can I collect my points?

Points are earning now, from the start of the season. Collecting opens soon, with a Veil upgrade; redeeming pays $VEIL after the season. Until then nothing is lost, and the app shows what you have accrued.

Why does a send sometimes show the token?

When you have no private SOL, the relayer is paid in the token you’re sending, which names it. Shield a little SOL to keep sends fully hidden.

$VEIL token
What is $VEIL?

The official token of the Veil platform. 100% of Veil’s revenue buys $VEIL on the market and burns it, so the token is tied directly to how much the platform is used. Official contract: HgTGdc29D5bDMrDvsCLnorxz899VyDj7ZN7FPa6vpump.

How does the buyback and burn work?

100% of the protocol fees Veil earns buys $VEIL on the open market, and those tokens are burned for good. More activity on Veil means more buybacks. The fee collection and every burn are public on-chain transactions that anyone can check, and the $VEIL token page shows the running totals live.

Can more $VEIL ever be created?

No. The mint authority is disabled, so no one, the Veil team included, can create new $VEIL. The freeze authority is disabled too, so no one can freeze anyone’s $VEIL. Burns only ever shrink the supply.

How do I know I have the real $VEIL?

Check the contract address: HgTGdc29D5bDMrDvsCLnorxz899VyDj7ZN7FPa6vpump. In the app, the real $VEIL carries the lilac Official platform token check. The app recognises it by its contract, never by its name, so copies with the same name never get the check.

Can I buy and hold $VEIL privately?

Yes. Open Trade and swap into $VEIL from your private balance. It lands in your private balance like any other token, with no link to your public wallet.

How do Veil Points turn into $VEIL?

Each season has a $VEIL pool (Season 1: 5,000,000). Every day pays out at most a 90th of it to that day’s points, the same rate for every point, and never more than a 50% yearly rate on the value shielded that day. What is left carries over. Your share is redeemable after the season, once redeeming opens with a later upgrade.

How much $VEIL can I expect from points?

It depends on how much is shielded in total. At $0.0035 per $VEIL, $1,000 shielded alone for 90 days earns about 0.7% of the pool (the 50% cap binds), while $500,000 shielded uses the whole daily budget, about 14% a year. The live yield and $VEIL per 1,000 points are in the Docs under Veil Points. Nothing here is financial advice.

Do I need $VEIL to use Veil?

No. Fees are paid in the token you move, and every feature works without holding $VEIL. Like any token, its price can fall as well as rise, and nothing here is financial advice.

Glossary

NoteA sealed record of a token amount you own. Your private balance is your notes.
CommitmentThe public fingerprint of a note, added to the Merkle tree. Reveals nothing about the note.
NullifierPublished when a note is spent, so it can't be spent twice. Unlinkable to the note's commitment.
RelayerA server that submits proofs and pays network fees. It can't alter what the proof allows.
Anonymity setThe crowd your activity blends into: other users of the same pool and token.
One-time addressA fresh Solana address derived from your vault, used once for an exit or a payment.