| Term | Definition |
|---|---|
| Account abstraction | Transaction authorization and execution through a programmable account. |
| CCTP | Circle’s Cross-Chain Transfer Protocol, which moves native USDC through a source-chain burn and destination-chain mint. |
| Destination call | A contract call included in an intent’s route and executed during destination-chain fulfillment. |
| ERC-3009 | A token authorization interface that includes signature-based transfers. |
| ERC-7683 | Cross-chain order interfaces implemented by the EVM Portal’s origin and destination settlers. |
| Executor | The contract that runs route calls on behalf of the destination Portal. |
| Flash Intent | A same-chain intent fulfilled using its vaulted reward through the Local prover’s flashFulfill operation. |
| Gateway | Circle Gateway, which provides a unified USDC balance across supported chains. See Circle Gateway deposits. |
| Intent | A specification of destination-chain execution and the source-chain reward for completing it. |
| Intent hash | The identifier derived from the intent’s destination, route hash, and reward hash. |
| Intent type | A route shape represented in a quote’s steps[], such as a solver fill or a swap followed by a bridge leg. |
| Kitchen | The Sauce factory and execution coordinator used to create Pots and manage execution fees. |
| Orchestration | Coordination of contract actions. In same-chain Routes flash fulfillment, those actions use the intent’s vaulted funds. |
| Permit3 | A token-permission contract that supports signed transfer and allowance operations on one or more chains. |
| Portal | The Routes contract that coordinates publishing, funding, fulfillment, settlement, and refunds. |
| Pot | A Sauce account whose owner authorizes execution. On EVM, it executes a program through the chosen engine. |
| Programmable Address | A deposit address associated with a configured workflow that is processed after funding. |
| Programmable Transaction | A program that reads state and executes contract actions within one transaction. |
| Prover | A contract that exposes fulfillment evidence used to authorize a reward withdrawal. |
| Resource lock | Assets reserved for a particular operation. Routes uses per-intent vaults for rewards. |
| Reward | The source-chain assets offered to the claimant for fulfilling an intent, together with the creator, prover, and deadline. |
| Route | The destination execution instructions, including required tokens and contract calls. |
| Routes | Eco’s intent-based transfer and swap protocol. The Routes API returns quotes and execution instructions. |
| Sauce | Eco’s programmable execution system for EVM and SVM programs. See Sauce SDK. |
| SauceScript | The TypeScript subset compiled by @eco-incorp/sauce-compiler into Sauce bytecode. |
| Settlement | Release of an intent’s source-chain reward after the required fulfillment proof is available. |
| Solver | An operator that quotes or fulfills intents and claims their rewards. |
| Storage proof | Evidence that a value is present in a blockchain’s state. |
| V12 | The engine that executes Sauce bytecode. |
| Vault | A per-intent contract that holds the source-chain reward. |
| Verified Liquidity | A closed-access Eco offering. See Verified Liquidity for onboarding. |
Reference
Glossary
Definitions of terms used in the Eco documentation.