Privacy Architecture
Mathematical guarantees, zero-knowledge verification, and non-custodial privacy invariants across the Veil Network stack. Browser-side proving, zero centralized note logging, and non-blocking withdrawals.
Non-Custodial by Mathematical Invariant
Veil operates entirely through decentralized smart contracts on Robinhood Chain. When you swap or deposit funds into the shielded pool, your assets are cryptographically accounted for via a LeanIMT Merkle tree. Neither Veil, relayers, nor guardians hold custody of your assets. The VeilShieldRouter enforces a strict 0-held custody invariant, ensuring no user funds ever linger in router storage.
Client-Side Proving & Zero Server Logging
All cryptographic secrets, nullifiers, and notes are generated locally in your browser using cryptographically secure randomness (Web Cryptography API). At no point are private notes, nullifiers, or secret keys transmitted to any external server or indexer. Proof payloads are assembled client-side; Groth16 zk-SNARK verification operates trustlessly on-chain on Robinhood Chain.
Client-Side Self-Relay & Decoupled Settlement
Withdrawals are broadcast directly via client-side self-relay from your browser wallet to the VeilZkRouter contract. All transaction parameters (pool, minimum amount out, recipient address, and fees) are cryptographically bound to the public input context hash of the ZK proof. Destination balances are decoupled from origin deposit notes inside the zero-knowledge pool. Users are advised to submit self-relayed withdrawals using distinct operational wallets to prevent linkability at the caller layer.
Non-Blocking Withdrawal Invariant
Veil contracts guarantee immutable, censorship-resistant withdrawals. While protocol guardians may pause incoming deposits in an emergency, withdrawal mechanisms can never be paused, censored, or frozen under any circumstance.