Veil logo

Confidential · Compliant · On-chain

Private, compliant settlement for tokenized real-world assets.

Veil turns a tokenized asset into an encrypted holding — ownership, balances and transfers hidden — while KYC, issuer controls and authorized-auditor view keys stay fully intact. The confidential settlement layer for institutions on Ethereum, other EVM chains and Stellar — with every private transaction proven and settled on Starknet.

For EVM & Stellar platforms · Execution layer: Starknet · SNIP-36 in-protocol proofs · Stwo STARK — no trusted setup · EVM wallets, no Starknet account · Live on Sepolia

The blocker

RWA can't run on a chain that exposes every position.

Front-running

Visible order flow and on-chain positions get picked off — institutions get worse execution the moment they accumulate.

Client-data exposure

A wallet tied to a real client makes its holdings permanent public data, colliding with GDPR, bank secrecy and fiduciary duty.

Institutions stay away

Regulated firms legally cannot trade where positions are public. The serious flow never arrives on a transparent chain.

Privacy here isn't a feature. It's the precondition for institutional volume.

The layer

You run the platform. Veil is the confidential settlement underneath.

Veil isn't an exchange or an issuer. Exchanges, issuers, funds and desks keep their product, users and operations on Ethereum, another EVM chain or Stellar — and Veil settles the result privately and compliantly, with Starknet as the execution layer underneath.

YOUR PLATFORMExchange · Issuer · Fund · Desk — product, users, UX
▲   PRIVATE, COMPLIANT SETTLEMENT   ▼
VEILHidden positions · Issuer rules + controls · Auditor view keys · Provable on-chain
EVM CHAINS · STELLAR — where your issuers and investors are. Connect through the Veil Bridge and keep your wallets. Stellar is coming next.
STARKNET— the execution layer. Veil's private proofs run and settle here; Veil operates it for you.

What you get

Privacy by default. Disclosure only when the law demands.

Encrypted holdings

A tokenized asset becomes an encrypted note on-chain — ownership, amounts and transfers hidden from everyone but you and authorized auditors.

Issuer rules, enforced privately

Every transfer is proven to satisfy the issuer's rules — eligibility, freezes, pause and transfer rules — enforced privately, inside the proof.

Issuer controls preserved

Freeze and forced-transfer (recovery / clawback) execute even on an encrypted holding. Issuers never give up control.

Auditor view keys

Selective, provably-scoped disclosure on lawful request — the auditor reads one user, never the uninvolved rest.

Private atomic DvP

Asset-for-cash settles atomically, with the maker's limit price and per-token conservation enforced on-chain.

SNIP-36 proofs

Each private action is proven with the Stwo STARK prover and verified in-protocol through SNIP-36 — no trusted setup, post-quantum, no new chain.

For EVM and Stellar platforms

Your issuers and investors stay where they are. The Veil Bridge carries permissioned tokens from Ethereum and other EVM chains into Veil and back over LayerZero V2, and investors sign with the EVM wallets they already use — no Starknet account. Stellar support — Stellar wallets and classic Stellar assets through the Stellar Asset Contract — is built and coming next.

See the EVM integration docs →

Supported tokens

The token standards Veil supports.

Permissioned ERC-20

Rule-gated

The issuer's rules contract decides who may hold, freezes, pause, whether transfers are on, and each transfer. Rules that depend on the sender's balance — locked amounts, investor caps, full-balance transfers, minimum holdings — are enforced inside the proof.

Permissioned ERC-20

Allowlisted

Every holder must hold the issuer's allowlist role, and every movement needs the token unpaused and both sender and recipient on the list — the same check as the token's own transfer hook.

Security token

ERC-3643

Eligibility and can-transfer are checked against the token's own identity registry and compliance contract, together with pause and freezes, plus the pool's optional country policy.

Unique assets

ERC-721

For one-of-a-kind tokenized assets such as real estate. Each token is held in Veil's dedicated ERC-721 pool as an encrypted note that its owner can transfer privately, approve someone else to transfer, or withdraw to a public address.

How it works

From tokenized asset to confidential settlement.

01

Deposit

A tokenized RWA leaves your chain through the Veil Bridge — from Ethereum or another EVM chain, with Stellar coming next — and becomes an encrypted holding in Veil.

02

Transact

Hold, transfer or trade through your platform — exchange, issuer, fund or desk. Any order flow or matching stays off-chain.

03

Settle

Veil proves and settles privately on Starknet, its execution layer — atomic DvP for trades, confidential transfers otherwise. Balances and counterparties stay hidden.

04

Disclose

Issuers keep freeze & recovery; auditors get view-key access only when the law requires.

Why Starknet

Why Veil runs on Starknet

Veil needs proofs that full contract logic ran correctly against current on-chain state. SNIP-36 provides that on Starknet, so Veil's execution and settlement happen there, while issuers and investors stay on EVM chains and Stellar.

Rules checked against current on-chain state

Veil has to check every private action against the issuer's rules and the user's holdings as they are on-chain. A SNIP-36 proof executes the transaction off-chain against a recent Starknet block and proves that execution. Its proof facts name that block, and Veil's settle rejects a proof whose base block is too old.

Full contract logic inside one proof

Each Veil action checks the token's rules, decrypts the user's encrypted notes and verifies the wallet's signature — EVM secp256k1 today, Stellar Ed25519 next. SNIP-36 proves ordinary contract code, so this logic is written as contracts rather than a custom circuit, and a change to an issuer's rules applies to the next proof.

Proofs verified on-chain

Settlement needs each proof checked on-chain. Under SNIP-36 the sequencer verifies the proof before the transaction propagates, and the contract reads its facts through a syscall. A full STARK proof — tens of thousands of field elements — is too large to fit in a single transaction, so verifying it inside a contract is not practical.

In SNIP-36's current phase, proofs are verified by Starknet consensus; verification on Ethereum through SHARP is a planned follow-up. Sources: SNIP-36, Starknet v0.14.2, Veil contracts.

How Veil compares

The only stack that is private, compliant and self-custodial at once.

ProtocolApproachConfidential holdingsIssuer rules + auditor disclosureRWA issuer controlsPrivate DvP settlementPublic chain · self-custody
VeilSTARK · executes on Starknet, serves EVM + Stellar✓✓✓✓✓
ZamaFHE · fhEVM (cross-chain)✓◐◐◐✓
Canton NetworkPermissioned · need-to-know✓✓✓✓✕
Azteczk-SNARK · privacy L2✓◐✕◐✓
Aleozk-SNARK · privacy L1✓◐✕✕✓
Railgunzk · EVM privacy system✓◐✕✕✓
Pantherzk · privacy DeFi✓◐✕✕✓
RenegadeMPC + zk · dark pool✓✕✕✓✓
Confidential EVMsTEE / FHE · Oasis, Inco, Fhenix, COTI✓✕✕✕✓
✓ supported◐ partial / emerging✕ not a focus

Closest overlaps: Canton Network leads institutional RWA but is permissioned — no public-chain access or self-custody; Zama brings FHE confidential tokens to Ethereum but isn't an RWA settlement venue with issuer controls and DvP; Renegade nails private trading but carries no compliance or issuer layer. Veil is the only one combining confidential holdings, issuer-rule compliance with auditor disclosure, issuer controls, and private DvP on a public, self-custodial chain — for platforms on EVM chains and Stellar, executed on Starknet.

Positioning as of mid-2026, by each project's primary design focus — not a feature-by-feature audit. "Confidential EVMs" groups TEE/FHE infrastructure (Oasis Sapphire, Inco, Fhenix, COTI). Veil is live on testnet (Starknet Sepolia, with the Veil Bridge to Ethereum Sepolia) and pending independent audit. Sources: project docs, Messari, CoinGecko, Canton Network.

Integration docs

Integrate from EVM. Your investors keep their EVM wallets.

EVM platforms add Veil through the Veil Bridge and integrate only on the EVM side. Veil deploys and operates everything on Starknet.

  • ✓No new Starknet wallet. The investor's existing EVM wallet holds the private position in Veil, under the same address. Nothing to create, fund or link.
  • ✓No Starknet key or gas. The wallet signs each Veil action with personal_sign; Veil's proof service proves and submits it on Starknet.
  • ✓Your records stay authoritative. One lockbox contract per instrument reads your identity registry, allowlist or rules engine live.

EVM integration guide

Veil Bridge for EVM platforms

For EVM platforms that issue, administer or distribute permissioned assets — tokenization platforms, transfer agents and fund platforms. Rule-gated and allowlisted ERC-20s, plus ERC-3643, with Solidity and Veil SDK code for every step.

  • Architecture
  • Lockbox contract
  • Instrument onboarding
  • Bridge in & out
  • USDC cash leg
  • Eligibility sync
  • Lawful-access audit
  • Security model
Read the guide ↗

Team

Team

Esdras Santos

Founder, Veil

Esdras Santos

Previously founder of Typhoon, the first private payment protocol on Starknet.

Apply for the pilot

Prove a confidential RWA market end-to-end — at zero risk.

We run a low-risk pilot entirely on testnet for platforms on Ethereum and other EVM chains (Stellar coming next): private positions, compliant settlement, issuer controls and auditor access. Contracts are deployed and the SDK is ready — it's mostly integration.

  • ✓Zero production exposure, zero regulatory exposure.
  • ✓A working demo in a few weeks.
  • ✓For exchanges, RWA issuers, funds and institutional desks on EVM chains — and soon Stellar.

Prefer email? esantoz@protonmail.com

Pilot application

We use your details only to evaluate the pilot. No spam.