A transaction intent is a signed request that describes an outcome a user wants and the conditions that must be met, while leaving some execution details to a solver or filler. Intent-based systems can simplify routing, but each protocol defines its own order format, authorization, settlement, and safeguards.
How an Intent Works
A trade intent might say: exchange a specified amount of one asset for at least a stated amount of another before a deadline. The user signs the order or authorizes it through a wallet or smart contract. An application shares the order with eligible solvers, which look for a way to fulfill its constraints using available liquidity. A winning solver or filler executes the settlement, and the protocol checks the conditions it enforces.
Some systems group orders into auctions, match opposing orders directly, or compare several liquidity sources. Others coordinate actions across chains. The term “intent” describes the user-facing expression of a desired result; it does not mean every protocol uses the same mechanism or that a solver can change the user’s signed limits.
What Intents Can Change
Separating the requested result from the execution route can let solvers search more than one pool or venue, handle transaction details, or compete to provide a settlement. In some designs, this can improve execution or make a swap easier to submit. Cross-chain intent designs can also coordinate source- and destination-chain steps through a solver.
These benefits are design-specific. Intents do not automatically remove fees, make a trade gasless, guarantee the best price, eliminate MEV, or make cross-chain transfers trustless. A protocol may still depend on a limited solver set, an off-chain order service, an escrow contract, a bridge, a resolver, or assumptions about settlement finality.
Checks and Risks
Before signing, inspect the assets and amounts, minimum output or other constraints, expiration, chain and contract permissions, and whether the authorization can be reused or cancelled. For cross-chain orders, check what happens if only one side executes, how refunds work, who holds funds during settlement, and which bridge or solver assumptions apply.
ERC-7683 is a draft standard for a solver-facing representation of cross-chain orders; it does not define or guarantee the safety of every intent protocol. Users still need to assess the specific contracts, signers, solvers, and settlement path they use.
Related Terms
See Also
- How Do Crypto Bridges Work — And Why Are They Such a Hack Target? — explains bridge and settlement assumptions that may matter when an intent spans chains.
- Are Layer 2 Networks Actually Decentralized? — examines how operators and control points affect the systems where orders may settle.
- What Is MEV — And Why Every Ethereum Transaction Is a Game — provides context for transaction ordering and value extraction around execution.
Sources
- CoW Protocol: Intents — explains signed user constraints, solver competition, order matching, and protocol-specific settlement behavior.
- ERC-7683: Cross-Chain Intents — specifies a draft solver-facing interface and describes how protocols retain flexibility in order creation and settlement.
- CoW Protocol: Signing Schemes — describes how off-chain orders are authenticated and bound to their parameters.