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.

Eco provides developers with a complete operating system for programming stablecoin flows across chains. Rather than treating cross-chain transfers as isolated bridge transactions, Eco enables atomic, composable operations that execute according to your exact requirements — enabling applications and strategies that simply weren’t possible before. Stablecoins are natively issued on 16+ chains, creating 240+ directional pairs for value movement. Eco gives developers a single API for moving them: a non-custodial intent network, a competitive solver market, and a programmable surface for deposits, swaps, and arbitrary destination calls.

What you can build today

ProductUse it toBest for
RoutesMove and swap stablecoins across chains in real timeWallets, DEXs, payment apps, cross-chain DeFi
Programmable AddressesGive users a static address that auto-routes deposits to the right chain or balanceExchanges, neobanks, protocol deposits, Gateway funding
Programmable TransactionsEmbed decision logic into a single transaction — no contract deploymentAggregators, MEV-resistant routing, AI-agent execution
Orchestration (preview)Compose routing + liquidity + compliance behind a single APIEnterprise treasury, regulated payments, agentic flows

How it fits together

What makes Eco different

Eco is not a bridge. Bridges pass messages; Eco delivers outcomes with cryptographic execution guarantees. Four design choices set it apart. Non-custodial by construction. Every intent is a Vault — a deterministic CREATE2 contract that holds reward tokens until proof of fulfillment. There is no protocol-owned account. Refunds are permissionless and run independently of Eco. For institutional signers, funding looks like a single ERC-20 transfer to a precomputed address — no EIP-712 signature, no Permit2 approval, no contract interaction. Permissionless and immutable. The Portal is a non-upgradable factory. No proxy pattern, no admin keys, no upgrade path. Any wallet, app, or solver can join. Compliance is enforced at the solver-selection layer, not in the contract — and provers are modular, so users choose the security model of their own intent. Dual-mode execution. Most intent systems only do one thing: a solver fronts capital and delivers your outcome. Eco does that — and can also fulfill an intent without a solver by routing the user’s own vaulted funds through underlying infrastructure inside a single transaction (flashFulfill via the Local Prover).
TierConditionModeCapital required
1Solver available, better pricingSettlementSolver capital
2Solver available, no pricing edgeOrchestrationGas only
3No solver availableSelf-solve via local intentGas only
Transitions between tiers are transparent. System availability equals chain availability, not solver availability. Runtime intelligence. Most onchain operations bake the route into the transaction at signing time. By the time the transaction lands, the chosen path may not be optimal. Eco’s Programmable Transactions layer (Sauce) lets a single transaction collect data from multiple contracts, choose between paths, and execute the optimal one — all atomically, without deploying a contract. This is what makes “best execution” a runtime claim, not a marketing one.

Bridge vs Eco

BridgeEco
Wraps tokens, mints on the destinationDelivers the requested asset, no wrapping
Custodied or LP-pool collateralPer-intent vault, released only by proof
Failure leaves you with wrapped tokensFailure refunds the original asset
Fixed route, baked at signing timePath picked at execution time by competing solvers
One messaging stack, take it or leave itSix provers; user picks per intent

What this gets you

  • Predictable settlement. No bridge limbo, no partial states, no support tickets about stuck wraps.
  • Stablecoin-grade speed. Solver competition + dual-mode means typical fulfillment in 20–40 seconds even when no solver is willing to front capital.
  • Compliance-ready. Solver-selection layer enforces address screening, AML, region-based rules — without modifying the Portal.
  • Audit-stable. The Portal you integrate against today is the Portal you’ll integrate against in five years.

Where to go next

Choose your product

Match your use case to one of the four products in 30 seconds.

Quickstart

Move your first USDC across chains in 5 minutes.

Architecture deep-dive

Portal, Vault, Executor, and the prover stack.

Solutions for you

Persona-shaped guides — wallets, protocols, PSPs, exchanges, issuers, treasuries, solvers, AI agents.