What is Veilpay and how does it work?

Veilpay is a non-custodial crypto vault that uses EIP-5564 stealth addresses and zero-knowledge proofs to enable private payments across 7+ blockchains including Stellar, Monero, Zcash, Ethereum, Solana, Base, and Arbitrum. Your private keys never leave your device.

What are stealth addresses and how do they provide privacy?

Stealth addresses (EIP-5564) generate a unique, one-time address for every incoming transaction, breaking on-chain linkability. This ensures your public financial history remains private on transparent networks by preventing transaction tracing.

How do zero-knowledge proofs enhance privacy?

Zero-knowledge proofs allow us to mathematically verify that a payment is valid without ever revealing the sender, receiver, or transaction amount to the public ledger. Your transactions remain cryptographically private from end to end.

Is Veilpay non-custodial and does it require KYC?

Yes, Veilpay is fully non-custodial. Your private keys never leave your device, and no KYC (Know Your Customer) verification is required. You maintain complete control over your assets.

Which blockchain networks does Veilpay support?

Veilpay supports privacy-native assets like Stellar, Monero, and Zcash, alongside transparent chains including Ethereum, Solana, Base, Arbitrum, and others. All blockchains are integrated into a single unified interface.

Privacy-chain roadmap

Veilpay’s privacy-chain roadmap is staged. Each chain requires separate engineering, security review, compliance review, UX, operations, and incident response planning.

Delivered track: Private XLM on Stellar

Private XLM is generally available on Stellar Mainnet in supported Veilpay releases. Continued work covers independent audit evidence, operational hardening, recovery performance, provider resilience, and incident readiness.

Ongoing controls:

native proof generation and device benchmarks
audited circuits and contracts
mainnet deployment ceremony or accepted trusted setup model
value caps
kill-switch
note-secret recovery UX
monitoring and incident response

Future track: Monero

Monero would require wallet integration, address/payment ID handling strategy, node or provider architecture, transaction monitoring, balance reconciliation design, and compliance review.

Future track: Zcash

Zcash would require shielded-address UX, viewing-key strategy, memo handling, note scanning, light-client or provider strategy, and balance reconciliation design.

Future track: Midnight

Midnight would require a separate architecture review when its developer tooling, privacy model, and production readiness are finalized.

Roadmap rule

Future privacy-chain tracks must not be described as production-live until their engineering, security, operations, compliance, and user-recovery requirements are met. Availability and external-audit claims are documented separately.