At a glance
What makes Veilify different
Wallet-native. Other designs ask the user to hold a new key, a new note, or a new app. Veilify proves the wallet’s own ECDSA signature inside the circuit, so the wallet stays the only spending authority. Account-free keys. Viewing keys come from a typed-data signature. Signing the same message again regenerates them. There is nothing to lose. Exit timing as a feature. Timing is a strong correlation signal, and most pools leave it entirely to the user. Veilify offers round withdrawals that leave together at scheduled times, and staggered withdrawals that spread one withdrawal across several rounds. Compliance without custody. The gatekeeper can approve or reject a deposit. It cannot move pooled funds, and it cannot stop a depositor from reclaiming a pending deposit.Trade-offs
A relayer and proxy are in the path
A relayer and proxy are in the path
Gas abstraction and wallet-native UX need an RPC proxy and a relayer. A fee-less withdrawal can be self-submitted to the contract, but the standard flow uses Veilify Network infrastructure. See Threat Model.
Rounds are policy, not consensus
Rounds are policy, not consensus
The contract does not enforce round timing. You trust the Veilify Network service to follow the schedule you selected.
Withdrawal amounts and recipients are public
Withdrawal amounts and recipients are public
Leaving the pool always reveals what arrived where. Round amounts, fresh addresses and waiting help. See Privacy Best Practices.