Skip to main content
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.

​
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

CapabilityProduct
Deterministic EVM address that auto-bridges to SolanaSolana Deposit Addresses
Fast gasless deposits into Circle GatewayCircle Gateway Deposits
Cross-chain withdrawal infra without per-chain deploymentRoutes API
Atomic refunds if a withdrawal failsVault model
Use caseUse
Solana withdrawalsSolana Deposit Addresses
Gateway-funded withdrawalsCircle Gateway Deposits
Withdrawal to any supported EVM chainRoutes API
Onramp → end chain in one stepProgrammable Addresses

​
Patterns

​
”Withdraw USDC to Solana” with one EVM transfer

Per user, generate a Solana deposit address derived from their Solana wallet. Store the EVM address. When the user withdraws to Solana, your hot wallet sends a normal ERC-20 transfer to that EVM address. The address auto-bridges to the user’s Solana wallet. → Recipe: Auto-route deposits to any chain

​
Fast deposits into Circle Gateway

Onramp partner sweeps customer USDC into Circle Gateway on Polygon for unified treasury management. Use Circle Gateway Deposits for 20–40 second settlement, gasless from the source chain. → Recipe: Gasless USDC into Gateway

​
Withdrawal infra without N integrations

Instead of running per-chain withdrawal infrastructure, route every withdrawal through Routes. One integration, every supported chain.

​
Get started

→ Solana Deposit Addresses, the most common starting point