What is Eco?

Building cross-chain stablecoin flows today means trusting bridges that wrap tokens, custody funds, and fail mid-transaction. Eco gives developers a single API for moving stablecoins across chains: non-custodial, composable, and guaranteed to execute exactly as specified or refund automatically. Stablecoins are natively issued on 16+ chains, creating 240+ directional pairs. Eco handles the routing, solver competition, and destination logic so you don’t have to.

​

What you can build today

​

How Eco is Built

Eco delivers programmable stablecoin outcomes, guaranteed. Four design choices make this possible. Non-custodial by construction. Every intent on Eco is a Vault, which keeps the whole protocol non-custodial and user and solver funds safe. Each vault is a deterministic CREATE2 contract that holds funds until proof of fulfillment, and 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. Permissionless and immutable. Anyone can build on Eco, and the contract you integrate against today behaves the same way years from now. 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 rather than in the contract, and provers are modular, so users choose the security model of their own intent. Dual-mode execution. Your transfer goes through as long as the chains are live, even when no solver is willing to take it. 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 funds through underlying infrastructure inside a single transaction (see Local Prover). Transitions between tiers are transparent. System availability equals chain availability, not solver availability. Runtime intelligence. You get the best execution available the moment your transaction lands, not a path locked in when you signed. Most onchain operations bake the route into the transaction at signing time, so by the time it lands the chosen path may no longer be optimal. Eco’s Programmable Transactions layer lets a single transaction collect data from multiple contracts, choose between paths, and execute the optimal one, all atomically and without deploying a contract. This is what makes “best execution” a runtime claim, not a marketing one.

​

What building on Eco ensures

• Predictable settlement. No bridge limbo, no partial states, no support tickets about stuck transactions.
• Stablecoin-grade speed. Solver competition and dual-mode mean typical fulfillment in 20–40 seconds even when no solver is willing to front capital.
• Compliance-ready. Add address screening, AML, and region rules without touching your integration.

​

Where to go next