Intents
A pattern in which users sign a desired outcome ("swap X for at least Y") and let solvers compete to execute it optimally across chains and venues. Powers cross-chain UX in protocols like CoW Swap and Across.
How intents differ from transactions
Traditional Ethereum transactions are imperative: "execute this exact contract call with these exact parameters." The user specifies every step.
Intents are declarative: "I want this outcome." The user signs an intent describing the desired result; specialized actors called "solvers" compete to deliver it.
Example contrast:
- Transaction — "Call Uniswap V3's swapExactTokensForTokens with input X, minimum output Y, deadline Z."
- Intent — "I want at least 1,000 USDC on Arbitrum, paying with at most 0.3 ETH on Ethereum."
The intent leaves the path open. Solvers might fulfill it through a single DEX swap, multi-hop routing, cross-chain bridging combined with a swap, or any other approach that meets the user's stated constraints.
Why intents matter
Several practical benefits:
- Better prices. Solvers compete; users get the best execution path automatically.
- Cross-chain UX. Intent-based protocols can fulfill orders across multiple chains without user-managed bridges.
- MEV reduction. Intents are typically submitted off-chain to solver networks rather than into public mempools, reducing front-running and sandwich attack risk.
- Gas abstraction. Solvers can pay gas; users can pay in any token rather than needing to hold native gas tokens on every chain.
- Composability. Complex multi-step operations (refinance + bridge + swap + deposit) can be expressed as a single intent.
Major intent-based protocols
A few in production:
- Across Protocol — fastest-growing intent-based bridge. Users specify "I want X tokens on chain Y"; solvers fulfill with their own liquidity, getting reimbursed by the canonical bridge later.
- CoW Protocol (CoW Swap) — pioneered the intent-based DEX model on Ethereum. Solvers batch user orders to find optimal execution.
- UniswapX — Uniswap's own intent-based extension launched 2023.
- 1inch Fusion — 1inch aggregator's intent-based mode.
- Anoma — broader research project around intent architecture; ongoing development.
- Various aggregators — many DEX aggregators have moved toward intent-style routing internally.
The approach has spread quickly through 2024-2025; intent-based volume is now a meaningful share of DEX activity.
How solver competition works
The typical pattern:
- User signs an intent expressing desired outcome.
- The intent is shared with a network of solvers (off-chain or on a private mempool).
- Solvers compute optimal fulfillment paths and submit bids.
- The protocol selects the winning solver — usually the one offering the best execution for the user.
- The winning solver executes the necessary on-chain operations to fulfill the intent.
- User receives the desired outcome; solver collects any surplus or fees.
Solvers are sophisticated actors — typically running optimization algorithms across many DEXes, lending protocols, and bridges to find the best path.
Cross-chain intents
The most compelling use case is cross-chain UX:
- User on Ethereum wants USDC on Arbitrum.
- Traditional flow — bridge ETH to Arbitrum (slow), swap to USDC. Multiple transactions, gas on both chains, waiting time.
- Intent flow — sign a single intent. Solver provides USDC on Arbitrum from their own liquidity. User signs once; gets the outcome.
The solver bears the bridging cost and timing risk; user gets clean UX. Across has demonstrated this works at scale, processing hundreds of millions in daily volume.
Intent vs. order
Some related concepts that get conflated:
- Limit order — "Buy when price reaches X." Specific instruction.
- Market order — "Buy now at best price." Direct execution.
- Intent — "Get me this outcome." Solvers figure out the path.
Intents are more flexible than orders. A limit order has a specific destination DEX and specific parameters; an intent has a desired outcome and lets the system figure out how to deliver it.
Risks specific to intents
A few concerns:
- Solver counterparty risk. Some intent flows have solvers fronting capital; if a solver fails, fulfillment can be delayed or fail.
- Centralization. Solver networks tend to be small at first, with a few sophisticated operators dominating. Whether decentralized solver markets emerge is unclear.
- Complexity. Intents are flexible but also opaque. Users may not understand what's happening behind the scenes.
- MEV redistribution. Intents reduce some forms of MEV but introduce others. Sophisticated solvers may capture surplus that users don't realize they're missing.
Where intents are heading
Several active development directions:
- Solver-network protocols — building infrastructure to coordinate solver competition across many applications.
- Cross-rollup atomicity — intents that execute across multiple Layer 2s atomically.
- Account-abstraction integration — combining account abstraction with intent submission for clean UX.
- Generalized intents — beyond swaps and bridges, expressing arbitrary on-chain outcomes.
- Privacy-preserving intents — encrypted intents that solvers can fulfill without seeing all details.
The category is moving fast. The architectural pattern (declarative outcomes + competitive solvers) is increasingly viewed as the future of crypto UX, displacing imperative transactions for many use cases.
What this means for users
For typical users:
- You probably already use intent-based protocols without realizing it. Many DEX aggregators, bridges, and wallets route through intent-based infrastructure under the hood.
- Better execution — most users get measurably better prices through intent-based protocols than through naive routing.
- Cleaner UX — multi-step crypto operations often collapse into single signatures.
- Trust shifts — instead of trusting specific contracts, users trust the solver network and the protocol selecting solvers.
For developers, intent-based architectures change how dApps are built. Instead of orchestrating multi-step transactions in user code, applications express user goals and let infrastructure handle execution. This is a meaningful UX upgrade comparable in scale to the move from manual gas-price management to EIP-1559.