The pain you’re solving
- Manually monitoring and rebalancing across chains is operationally expensive
- AMM-based bridges have high slippage at size
- Idle treasury earning ~0%
- Risk of bridge failure leaving capital in wrapped form mid-flow
What Eco gives you
| Capability | Product |
|---|---|
| Programmatic cross-chain rebalancing with guaranteed execution | Routes API |
| Earn yield on idle treasury | Crowd Liquidity |
| Conditional execution (“rebalance when X”) | Programmable Transactions |
| Atomic, all-or-nothing rebalance flows | Vault model |
| Compliance / multi-sig integration | Orchestration |
Recommended product mix
| Use case | Use |
|---|---|
| Treasury rebalancing service | Routes API |
| Idle-stable yield | Crowd Liquidity |
| Conditional/threshold execution | Programmable Transactions |
Patterns
Threshold-triggered rebalance
Run a service that watches per-chain utilization. When chain A < 20% AND chain B > 80%, publish a Routes intent moving USDC. Atomic execution means no half-state to reconcile. → Recipe: Treasury rebalancingYield on idle USDC
Deposit treasury USDC into Crowd Liquidity. Solvers flash-borrow against it for fulfillment; you earn fees on actual usage. No lockup — withdraw anytime. → Crowd LiquidityMulti-sig rebalance with audit trail
Use Permit3 to authorize the rebalance flow with a single multi-sig signature, then trigger Routes intents over the lifetime of the authorization. Every leg is provable onchain.Get started
→ Routes API — programmatic intent publishingRead next
Routes API
Programmatic intent publishing.
Permit3
Multichain authorization with one signature.
Treasury rebalancing recipe
End-to-end rebalancer pattern.