Glossary/Infrastructure

Intent-Based Architecture

Intent-based architecture is a design where users sign a declarative statement of the outcome they want — "swap X for at least Y" — and a competitive network of off-chain solvers figures out and executes the path. The user specifies the what; solvers handle the how.

What it is

Intent-based architecture flips the default model of blockchain interaction. In the old model, you sign an imperative transaction: call this contract, then that one, with these exact parameters, and pay gas whether it succeeds or not. In an intent model, you sign a declarative message — "I want to sell 10 ETH for at least 38,000 USDC before this deadline" — and hand it to a network of competing agents called solvers who find the execution path and submit it on your behalf.

The distinction sounds academic. It isn't. Decoupling the goal from the route is what lets these systems route across DEXs, bridges, and lending markets, batch trades together, and absorb gas and failure risk on the solver's side rather than yours.

How it works

The flow is consistent across protocols. You sign an off-chain order describing inputs, the minimum acceptable output, and a deadline. That order is broadcast to a solver network. Solvers compete — usually through a Dutch auction or batch auction — to fill it on the best terms. The winning solver bundles the on-chain transaction, pays the gas, and delivers the result. You sign once and either get the outcome you specified or nothing.

The leading implementations differ in their auction mechanics. CoW Protocol runs roughly 30-second batch auctions and matches "coincidence of wants" — when two users want opposite trades, they settle against each other at no AMM fee. UniswapX uses a Dutch auction tied to Uniswap's retail distribution. 1inch Fusion blends RFQ quoting with auctions. Together these handle billions in monthly volume through solver auctions.

Why it matters

The core win is that the user leaves the adversarial mempool. When your trade never sits in a public pool waiting to be sandwiched, MEV becomes the solver's problem, priced into the quote you already accepted. You also stop paying for failed transactions, and cross-chain actions collapse into a single signature instead of a bridge-then-swap dance.

This is also the substrate AI agents will execute on. An autonomous agent reasons in outcomes, not calldata — "rebalance this portfolio" maps far more naturally onto an intent than onto a hand-built transaction sequence. See AI Agent and Account Abstraction, which together make agent-driven, gasless intent flows practical.

Key risks and tradeoffs

In my view the honest framing is that intents move trust rather than removing it. A few things to weigh:

  • Solver centralization. Solvers that also build blocks get an information edge, and that edge compounds. Paradigm flagged this in 2023: the better a solver routes, the more it wants to be a block builder, and the cycle tightens. Most networks counter with bonding, slashing, and permissioned solver sets — which trades decentralization for execution quality.
  • MEV isn't gone. Solvers still see your intent. Without encrypted mempools or threshold encryption, a permissionless intentpool can reproduce the same extractive behavior it was meant to fix.
  • Opaque execution. You're trusting that the winning solver actually found the best fill, not just a fill that's best for them. Verification tooling here is still thin.

Current state (2026)

The standardization race is well underway. ERC-7683, the cross-chain intents standard from Across and Uniswap Labs, is the focal point — the Open Intents Framework built around it has support from Arbitrum, Optimism, Base, Scroll, and Polygon. Per Across's own reporting, ERC-7683 orders now make up the large majority of its volume, and CoW Protocol shipped a 7683 adapter in early 2026. Wallets followed: Safe, Argent, and Rabby emit 7683 orders, and MetaMask added native support in version 12.4.

The interesting unsolved question isn't adoption — it's whether the solver layer ends up as concentrated as the block-builder market it grew out of. Watch where the bonds and the block-building stack consolidate; that's where the real power in this design will sit.

This entry is educational and not financial advice. Protocols named are illustrative, not endorsements.

Frequently asked

What is the difference between an intent and a transaction?

A transaction is imperative — it specifies the exact steps and contract calls to execute. An intent is declarative: it states the outcome you want and your constraints, leaving the execution path to a solver. You sign the goal, not the route.

Do solvers have custody of my funds?

No. In well-designed intent systems the settlement contract enforces your constraints, so a solver can only fill your order on the terms you signed or not at all. The trust you extend is about execution quality — whether you got the best fill — not custody of assets.

What is ERC-7683 and why does it matter?

ERC-7683 is a standard from Across and Uniswap Labs for expressing cross-chain intents in a common format, so solvers and apps interoperate instead of fragmenting. As of 2026 it's backed by the Open Intents Framework and supported across major L2s and wallets, making it the leading candidate for an industry-wide intent standard.

Sources