Core workflow
Cross-chain
A private balance is not confined to Solana. Veilo can spend from the pool and deliver the proceeds to an arbitrary address on seven EVM chains.
Where value can go
Veilo can spend from the pool and deliver the proceeds to an arbitrary address on Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain or Avalanche, in a chosen ERC-20 such as USDC, rather than only the native gas token of that chain.
| Property | Detail |
|---|---|
| Source | Your private balance on Solana |
| Destinations | Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche |
| Asset delivered | A chosen ERC-20 such as USDC, not only the native gas token |
| Destination type | A wallet, a contract, or an address a partner's system derives |
| Link to the depositor | None. The spend leaves the pool, not your wallet |
The destination does not have to be yours
It can be a contract, or an address a partner's system derives. This is the mechanism by which a private balance can reach systems that live entirely off Solana, including fiat off-ramps, brokerages and payment networks.
- Off-ramps. A provider that issues a deposit address per user can be paid directly from the pool.
- Contracts. A destination that is a contract call rather than a wallet works the same way.
- Payment networks. Settlement rails that expect an EVM address and a stablecoin need no knowledge of Veilo.
Funding works in the other direction too
Through integrated exchange and swap providers, value can move into a private balance without first being assembled in a public wallet of yours. That closes the loop: for many users there is no step at which their own public address has to hold the funds.
What is visible on the far side
Recovery
Cross-chain delivery is a multi-step flow, and multi-step flows get interrupted. Every flow has an explicit recovery path that returns funds to your private balance, no step leaves value stranded somewhere only a lost session could reach. See Private execution.