Summary: Eco is best cataloged as programmable stablecoin orchestration infrastructure rather than as a simple bridge, wallet UX layer, or single protocol. The official site and docs describe a broader stack for moving stablecoins across major chains and markets, simplifying multichain UX with gasless universal balances, and encoding routing or execution rules directly into transfers. The strongest product-level evidence in this pass came from Eco Routes, Permit3, and the public GitHub organization, which together show Eco packaging cross-chain intent execution, one-signature permissioning, and developer-facing automation into one stablecoin control plane.
What it does:
Provides a developer platform for bridging and swapping stablecoins across major chains, vaults, and markets with realtime routing and settlement language on the homepage
Offers Eco Routes, an intent-based cross-chain module where users publish desired outcomes, solvers fulfill them, provers attest to fulfillment, and rewards settle atomically on the source chain
Implements ERC-7683-compatible intent creation and fulfillment so developers can integrate through both Eco’s native interface and a standardized cross-chain order interface
Offers Permit3, a token-permission system that extends Permit2-style flows toward cross-chain approvals and transfers using one signed root plus per-chain proofs
Exposes stablecoin-abstraction and programmable-execution flows for global balance views, gasless spending, automatic source-chain selection, multi-step atomic execution, fallback paths, and policy-style execution controls
Key claims:
The homepage says Eco is “the stablecoin network that makes money programmable” and describes one developer platform connecting major chains, assets, and markets
The homepage presents three core outcomes: realtime money movement, simpler onchain UX through global balances and gasless transactions, and programmable execution with routing rules and fallback conditions
The Routes docs say Routes is an intent-based stablecoin bridging and swapping module where users express what they want, solvers compete to fulfill it, and cryptographic proofs ensure atomic settlement
The Routes docs say Eco implements ERC-7683 and supports multiple prover types, including Hyperlane, LayerZero, Metalayer, Polymer, CCTP, and a LocalProver for same-chain or orchestration flows
The Permit3 docs say Permit3 enables cross-chain token approvals and transfers with a single signature, using Unbalanced Merkle Trees while maintaining backward compatibility with Permit2
The stablecoin-abstraction docs say users can see one normalized balance across chains and spend with automatic source selection and gasless execution paid in stablecoins
The programmable-execution docs say developers can encode multi-step workflows, conditional routing, fallback paths, compliance checks, and treasury rules directly into stablecoin transfers
The public GitHub organization lists permit3, eco-routes, eco-routes-svm, and routes-cli, which reinforces that the product surface is implemented as live protocol and tooling repos rather than only marketing copy
Whitepaper: No canonical standalone Eco whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, docs for Routes and Permit3, the stablecoin-abstraction and programmable-execution use-case pages, and Eco’s public GitHub organization and repos; see ../whitepapers/eco-primary-sources-2026-05-03.md.