Publish one identity
Create separate viewing and spending keypairs. Share the public VEIL meta-address.
One public recipient identity. New on-chain destinations for every transfer. Only the recipient can detect which addresses belong to them.
ONE SHAREABLE VEIL IDNEW ADDRESS PER PAYMENTLOCAL VIEWING KEY SCANRECIPIENT SPENDING KEYSENDER WALLETONE-TIME ADDRESSThe public identity stays stable. The destination changes for every payment.
Create separate viewing and spending keypairs. Share the public VEIL meta-address.
The sender creates a fresh stealth address for that payment and publishes a compact announcement.
The recipient scans announcements, identifies owned addresses, then spends from them directly.
VEIL does not claim invisible transactions. It limits one specific leak: the public connection between a known wallet and a receiving address.
Read the privacy modelWallets and applications can prepare a private transfer, route payment and announcement atomically, and leave control with the recipient.
const transfer = await veil.prepare({
recipient: recipientMetaAddress,
amount: paymentAmount
});
await veil.send(transfer);Contracts, local key vault, sender flow, scanner, native ETH withdrawal
Robinhood Chain testnet contracts, username registry, wallet and scan validation
Live Robinhood Mainnet payments, usernames, production launch and monitoring
Official token launch after Mainnet Beta, using the publicly identified VEIL deployer wallet
SDK package, wallet modules, payment links, merchant and payroll pilots
Zero-knowledge private balances, hidden amounts and senders, relayers, production hardening
Start on Robinhood Testnet with test ETH, then switch to Robinhood Mainnet when you are ready to use real funds.