Cowrie Research

eco-primary-sources-2026-05-03

4 min read

Eco primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth is Eco’s official site and docs corpus, supported by the public GitHub organization and protocol/tooling repos.
  • The official materials consistently position Eco as a programmable stablecoin infrastructure layer spanning routing, permissions, UX abstraction, and conditional execution.

Primary-source snapshots

1) Official homepage

  • URL: https://eco.com/
  • Key excerpt:
    • Eco calls itself “the stablecoin network that makes money programmable.”
    • The homepage says developers can build stablecoin products without building stablecoin infrastructure.
    • It highlights three product outcomes: realtime money movement, simplified multichain UX, and programmable execution.

2) Routes overview

  • URL: https://eco.com/docs/getting-started/routes/overview
  • Key excerpt:
    • Routes is described as Eco’s intent-based stablecoin bridging and swapping module.
    • The docs say users create intents, solvers compete to fulfill them, and provers attest to fulfillment so settlement can happen atomically.
    • The page also says Eco implements ERC-7683 and supports multiple prover backends including Hyperlane, LayerZero, Metalayer, Polymer, CCTP, and a LocalProver.

3) Permit3 overview

  • URL: https://eco.com/docs/getting-started/permit3/overview
  • Key excerpt:
    • Permit3 is described as a token-permission protocol for cross-chain token approvals and transfers with a single signature.
    • The docs say it extends Permit2 concepts to multi-chain operations through Unbalanced Merkle Trees.
    • The page emphasizes cross-chain nonce handling, chain-specific proofs, and replay-protection/security controls.

4) Stablecoin abstraction use case

  • URL: https://eco.com/docs/getting-started/use-cases/stablecoin-abstraction
  • Key excerpt:
    • Eco says developers can give users a single stablecoin balance that works everywhere while abstracting away chains, gas tokens, and network switching.
    • The page describes automatic source selection, gasless execution paid in stablecoins, and Permit3-based permissions.
    • This was the clearest page for understanding Eco as a UX and orchestration layer above fragmented multichain balances.

5) Programmable execution use case

  • URL: https://eco.com/docs/getting-started/use-cases/programmable-execution
  • Key excerpt:
    • Eco says developers can encode exact execution requirements into stablecoin transfers with cryptographic guarantees.
    • The page describes multi-step atomic workflows, conditional branching, fallback paths, price and time constraints, circuit breakers, and treasury/compliance use cases.
    • This is strong evidence that Eco is packaging policy-style execution infrastructure, not only moving tokens between chains.

6) GitHub organization

  • URL: https://github.com/ECO
  • Key excerpt:
    • The org tagline says Eco is “the stablecoin network that makes money programmable across every major blockchain.”
    • Public repositories include permit3, eco-routes, eco-routes-svm, and routes-cli.
    • The repo mix supports the docs’ claim that Eco’s surface area spans permissions, routing, protocol logic, and developer tooling.

7) eco-routes repository

  • URL: https://github.com/eco/eco-routes
  • Key excerpt:
    • The repo README describes Eco Routes as an intents-driven, permissionless, trust-neutral protocol for incentivized cross-chain execution and proof.
    • It names the same user, solver, and prover roles described in the docs and references support for multiple messaging protocols.
    • It also highlights ERC-7683 compatibility, deterministic vault-based reward funding, and source/destination portal architecture.

8) permit3 repository

  • URL: https://github.com/eco/permit3
  • Key excerpt:
    • The repo README says Permit3 enables cross-chain token approvals and transfers with a single signature while maintaining Permit2 compatibility.
    • It adds detail about deterministic deployment address reuse across chains, witness functionality, allowance controls, and multi-token support.
    • This repo helped confirm that Permit3 is not merely a docs concept but a maintained implementation surface.

9) routes-cli repository

  • URL: https://github.com/eco/routes-cli
  • Key excerpt:
    • The CLI is described as a terminal tool for publishing cross-chain intents on Eco Routes.
    • The README explains intent publishing from source to destination chains and shows interactive prompts for route token, reward token, deadlines, and fulfillment watching.
    • This is a useful signal that Eco is building operator/developer tooling around the protocol rather than only publishing contract docs.

Working conclusion

Eco is best cataloged as programmable stablecoin orchestration infrastructure. The decisive evidence in this pass was the combination of official materials for Routes, Permit3, stablecoin abstraction, and programmable execution, plus a public GitHub footprint that shows live protocol and tooling repos behind those claims. The key distinction is that Eco is packaging routing, permissions, UX abstraction, and execution logic into one developer-facing control plane rather than shipping only a bridge, only a wallet abstraction layer, or only a token-permission primitive.

Graph View