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.

Indexer and jobs

Veilpay uses background workers for tasks that should not block API request/response paths.

Job categories

Chain polling and transaction detection.
Retry and dead-letter handling for failed background jobs.
Chain-specific indexing and recovery support for private-payment state.

BullMQ

BullMQ is used for queue-based job execution. Redis provides the backing store for queues, retry state, and coordination.

Chain indexer

The indexer package and backend chain-indexing jobs monitor networks for transaction status. Supported chain behavior differs by network, so integration code is split by chain family.

Private XLM state recovery

Private XLM uses the native client and configured Stellar infrastructure to recover private state. The app requires a verifiable, complete synchronization result before enabling state-changing private actions. Backend or archive indexing can improve recovery performance and provider resilience, but the UI must not treat an incomplete index as a current balance.