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.

The Routes protocol is a small set of contracts deployed on every supported chain, plus a modular settlement layer the user picks at intent-creation time.

​
The contracts

ContractRolePer-intent?
PortalSingle entry point — publish, fund, fulfill, prove, withdraw, refundOne per chain
VaultPer-intent escrow — holds reward tokens until proven fulfillmentOne per intent (CREATE2)
ExecutorStateless contract that runs user-specified destination callsOne per Portal
ERC-7683Standardized cross-chain order interface (origin + destination settlers)Built into Portal

​
The modular settlement layer

The Portal accepts any contract that implements the iProver interface. Six provers ship today; the user picks one per intent.
ProverSettlement methodBest for
CCTPIssuer attestationsUSDC routes, regulated flows
HyperlaneHyperlane ISMGeneral-purpose, fast
LayerZeroDVN consensusWide chain coverage
MetalayerCaldera MetalayerCaldera ecosystem
PolymerIBC light clientsTrust-minimized
LocalSame-chain flashFulfillSame-chain, orchestration mode

​
Information flow

​
Design principles

Non-upgradable. The Portal has no proxy, no admin keys, no upgrade path. Audited once, valid forever. Stateless executor. The Executor has no persistent storage. Each intent’s calls run in isolation — a malicious call cannot corrupt Portal state. Per-intent vaults. Funding is a vanilla ERC-20 transfer to a CREATE2 address. Cold wallets, hardware devices, multisigs, exchanges, PSPs all participate without changes. Modular settlement. New messaging protocols plug in via iProver without changes to Portal, vaults, or solver tooling. Cross-VM. EVM, SVM, and TVM are first-class. Address fields use bytes32 to hold any chain’s address format.

Portal contract

The main entry point — full Solidity surface.

Provers overview

How the modular settlement layer works.