Mainnet beta is the current phase
Protocol foundation and Robinhood Testnet beta are complete. VEIL is now in Robinhood Chain Mainnet Beta, followed by the $VEIL token launch.
The protocol must perform a real recipient-privacy function.
Every release must state what remains public.
Real-value usage expands through measured releases and live validation.
Protocol foundation
Build the complete recipient-privacy flow before expanding the protocol.
- ERC-5564 announcer contract
- ERC-6538 registry contract
- Local spending and viewing key generation
- Encrypted identity backup and restore
- Native ETH transfer preparation
- Announcement scanner and view-tag filtering
- Stealth key derivation and native withdrawal
- Separate Robinhood Testnet and Mainnet network profiles
- Atomic native ETH fee router with disclosed bounded pricing
The complete sender, scanner, and withdrawal flow works end to end.
Robinhood Chain testnet beta
Validate repeatable public testnet use before real-value mainnet activity.
- Testnet protocol contracts deployed
- Testnet username registry deployed
- Contract addresses and deployment blocks recorded
- MetaMask and injected EVM wallet support
- Scanning from a known deployment block
- RPC and wallet failure handling
- Identity recovery and backup checks
- Protocol fee quotes and treasury delivery validated
Test wallets can register, claim usernames, send, scan, receive, and withdraw without manual code changes.
Robinhood Chain mainnet beta
Operate VEIL on Robinhood Mainnet and harden the public product through live beta use.
- Mainnet registry, announcer, and fee router deployed
- Mainnet username registry deployed
- Robinhood Testnet and Mainnet switching live
- Username and VEIL-address payments on Mainnet
- Production website and domain launch
- Live send, scan, receive, and withdrawal validation
- RPC, wallet, and scanner monitoring
- Recovery and support flow hardening
Mainnet users can claim usernames, register identities, send, scan, receive, and withdraw reliably through the public website.
$VEIL token launch
Launch the VEIL ecosystem token only after the Mainnet Beta protocol is live and functioning.
- Publish the official token contract address through VEIL channels
- Launch from the same publicly identified VEIL deployer wallet
- State token supply, allocation, and permissions clearly
- Verify source code and ownership settings publicly
- Separate token activity from users' private payment identities
- Add the official token link inside the VEIL application
$VEIL is publicly verifiable, clearly documented, and connected to the live VEIL protocol without changing the payment contracts.
Privacy-preserving operations
Reduce the links users can create after receiving funds.
- Relayer design for controlled gas sponsorship
- Account abstraction compatibility
- Withdrawal timing and batching research
- Optional watch-only scanning mode
- Hardware-backed key storage research
- Multi-device identity recovery design
Any new feature has a defined threat model and does not weaken the base protocol.
Developer integrations
Make VEIL useful outside its own interface.
- Versioned TypeScript SDK
- Wallet integration module
- Payment request links
- Merchant checkout example
- Payroll and contributor-payment example
- Webhook-free local scanning worker
- Integration documentation and test vectors
A third-party application can integrate recipient privacy without importing VEIL's frontend.
Full privacy system
Extend VEIL beyond recipient unlinkability into a separate zero-knowledge privacy network.
- Zero-knowledge private balance model
- Hidden payment amounts and asset types
- Sender privacy and relayed transaction submission
- Private pool and note lifecycle design
- Selective disclosure and compliance proof research
- Dedicated proving infrastructure and performance work
- Production cryptography validation and protocol hardening
A production candidate demonstrates sender, recipient, amount, and asset privacy under a published threat model.
Roadmap items are not promises.
Security findings, chain changes, and test results can reorder or remove work. A smaller safe release is preferred over a larger fragile release.