Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 52 of 179

Intent-Based Architectures

Why CoW Swap, UniswapX, Across, and 1inch Fusion moved from 'sign a transaction' to 'sign an intent' — and how solver competition delivers better prices and MEV protection.

Beginner
8 min readUpdated July 2026Block Clarity Hub Editorial Team

The Old Way: You Pick the Path

Traditional DeFi swaps work like this: your wallet decides which DEX to use, which path through which pools, what the slippage tolerance should be, and submits a transaction with all of that hardcoded. If a better path emerges before your transaction lands, you don't benefit. If MEV bots see your transaction in the mempool, they can sandwich it. The user (or their wallet's router) is making every decision before submitting, then committing to it.

The New Way: You Sign What You Want

Intent-based architectures invert this. You sign a message saying 'I want at least 1.95 ETH for my 5,000 USDC, by [deadline].' The intent doesn't specify the path. Off-chain solvers compete to fulfill it — finding the best route through DEXes, bridges, AMMs, private quoter pools, even matching against opposite intents — and submit the winning execution on-chain. You get a price at least as good as your intent demanded, and often much better.

Where You Already Use It

CoW Swap was first to popularise this in production (since 2021). UniswapX (2023) brought it to Uniswap. 1inch Fusion (2022) brought it to 1inch. Across uses intent-based bridging. If you've used any of these, you've signed an intent. The user experience often looks identical to a regular swap — same wallet flow, same confirmation — but the on-chain settlement is different.

  • Old: sign a transaction with a specific route, slippage, deadline
  • New: sign an intent saying 'fulfill these conditions by this time'
  • Solvers compete off-chain to find the best execution
  • Used by: CoW Swap, UniswapX, 1inch Fusion, Across, many more

Key Takeaways

  • Intents declare what you want, not how to get it
  • Solvers compete to fulfill — competition pushes prices toward optimal
  • MEV resistance is structural: you signed a price, not a transaction in the public mempool
  • Already in production at major DEXes and bridges

Related Content

Hash Functions Compared

SHA-256, Keccak-256, Blake3, and Poseidon — which one each chain uses, why ZK systems needed a new family of 'arithmetic-friendly' hashes, and what tradeoffs each makes.

Stealth Addresses and Confidential Transactions

Privacy primitives that hide who's receiving what — from Monero's foundational stealth addresses to Ethereum's ERC-5564 and the legal context post-Tornado-Cash.

CDP Lifecycle

How collateralized debt positions work end-to-end — minting DAI against ETH, paying stability fees, surviving liquidations, and the structural lessons from MakerDAO's Black Thursday and Liquity's no-fee model.

Perpetual Swap Mechanics

How perp futures actually work — funding rates that keep them pegged to spot, mark vs index price, insurance funds that backstop losses, and the liquidation cascades that wreck overleveraged accounts in seconds.

MEV-Share Mechanics

How Flashbots' MEV-Share lets users share metadata about their transactions in exchange for a cut of the MEV searchers extract — a structural shift from 'searchers prey on users' to 'searchers and users share value.'

Solver Networks

How solver markets shape DEX prices, the competitive structure across CoW Swap, 1inch Fusion, Hashflow, and other venues, and why solver consolidation is the central debate of 2025-2026 DeFi market structure.

Liquidation Cascades

The mechanical structure of cascading liquidations — Black Thursday, May 19 2021, August 2024 — what amplifies them, who profits, and why over-leverage creates correlated risk across the entire DeFi stack.

Flash Loan Economics

Why flash loans exist, the legitimate uses (arbitrage, collateral swaps, refinancing), and how the same primitive that enables capital-efficient DeFi also enables governance attacks and oracle manipulation.

References & further reading