Skip to main content

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.

Treasury and yield managers care about three things: predictable execution at size, capital efficiency, and risk transparency. Eco’s vault-based settlement and Crowd Liquidity layer give you all three.

​
The pain you’re solving

  • Manually monitoring + 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

CapabilityProduct
Programmatic cross-chain rebalancing with guaranteed executionRoutes API
Earn yield on idle treasuryCrowd Liquidity
Conditional execution (“rebalance when X”)Programmable Transactions
Atomic, all-or-nothing rebalance flowsVault model
Compliance / multi-sig integrationOrchestration
Use caseUse
Treasury rebalancing serviceRoutes API
Idle-stable yieldCrowd Liquidity
Conditional/threshold executionProgrammable 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 rebalancing

​
Yield 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 Liquidity

​
Multi-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 on-chain.

​
Get started

→ Routes API — programmatic intent publishing