Skip to main content
DeFi protocols are limited by the chain they’re on. A vault on Arbitrum doesn’t see capital sitting on Optimism. Users abandon at the bridging step. Eco gives you cross-chain reach without deploying anywhere new.

​
The pain you’re solving

  • Users on chain A want to deposit into your vault on chain B but get lost in the bridge UI
  • Treasury sits idle on one chain while opportunities exist on another
  • Cross-chain rewards distribution forces users to claim on a chain they don’t use
  • Adding a new chain means deploying contracts, bridging liquidity, maintaining infrastructure

​
What Eco gives you

​
Patterns

​
”Deposit from any chain” button

User clicks Deposit on your Arbitrum vault. Your frontend builds a Routes intent with route.tokens = [USDC on Arbitrum] and route.calls = [approve(vault), vault.deposit(amount, user)]. User signs once on their source chain. The whole sequence executes atomically, or refunds. → Destination calls

​
Auto-rebalance treasury

Run a service that watches utilization on each deployed chain. When a threshold trips, publish a Routes intent moving USDC from over-supplied chain to under-supplied. Settlement guarantees mean no partial-state reconciliation. → Recipe: Treasury rebalancing

​
Withdraw to any chain

User specifies a withdrawal address on any supported chain. Your contract publishes a Routes intent funded from your treasury, with the user’s address as the recipient. User receives funds on their chain of choice.

​
Get started

→ Destination calls, the primary capability you’ll use