Exchanges and onramps face a structural problem: users want destinations on every chain, but you can’t run withdrawal infrastructure for each one. Programmable Addresses turn that into one EVM withdrawal that auto-routes anywhere.Documentation Index
Fetch the complete documentation index at: https://eco.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
The pain you’re solving
- Users want to withdraw to Solana, Polygon, Sonic, Ronin — you’d need a separate integration per chain
- Withdrawal failures generate the highest-volume support tickets
- Onramp users want their fiat to land on the chain where they actually use it
- Your treasury sits on chains you don’t actively operate on
What Eco gives you
| Capability | Product |
|---|---|
| Static EVM address that auto-bridges to Solana | Solana deposit addresses |
| Fast gasless deposits into Circle Gateway | Gateway Fast Deposits |
| Cross-chain withdrawal infra without per-chain deployment | Routes API |
| Atomic refunds if a withdrawal fails | Vault model |
Recommended product mix
| Use case | Use |
|---|---|
| Solana withdrawals | Solana deposit addresses |
| Gateway-funded withdrawals | Gateway Fast Deposits |
| Withdrawal to any supported EVM chain | Routes API |
| Onramp → end chain in one step | Programmable Addresses |
