1inch is not one liquidity pool or one exchange. It is an aggregation layer that can compare available liquidity sources and construct a route for a token swap. That can improve execution when liquidity is fragmented, but it also means a user must understand the displayed route, approvals, price impact and the difference between a normal onchain swap and an intent-based Fusion order.
Last reviewed: October 7, 2026. Supported networks, routes, tokens, Fusion availability and interface labels can change. Confirm the live quote in the official 1inch application before signing. This independent guide is educational and not financial advice.
What a DEX aggregator does
Liquidity in DeFi is distributed among pools, market makers and networks. A direct swap uses one selected venue. A DEX aggregator requests quotes from available sources and can select or split a path between them. 1inch describes its Pathfinder system as routing infrastructure that seeks an efficient swap path across supported liquidity sources.
For a larger trade, using several sources may produce a better quote than draining one shallow pool. For a small, liquid pair, a direct route can be simpler and may have similar results. The useful comparison is the complete live quote after costs, not a promise that aggregation is always superior.
How multi-DEX routing changes a swap
| Route type | Potential benefit | Trade-off to review |
|---|---|---|
| Direct pool | Simple path and fewer moving parts. | May have less favorable depth or price. |
| Split aggregation route | Can access liquidity from multiple sources. | More complex execution and gas considerations. |
| Fusion intent order | Resolvers compete to execute under stated conditions; may reduce public-mempool MEV exposure. | Execution timing and available route depend on resolver economics. |
A route is a calculation based on current liquidity and conditions. It can change before confirmation, and the output token can still be risky or illiquid. Read the actual assets, network, minimum received, price impact and gas estimate before approving anything.
MEV, front-running and Fusion
With a conventional public transaction, bots can observe a pending swap and try to reorder transactions around it. This can contribute to front-running or sandwich attacks, especially where price impact and slippage are high. 1inch Fusion uses an intent-based model: the user defines acceptable swap conditions and resolvers compete to execute the order. 1inch describes this as gasless for the user in supported Fusion flows and designed to reduce common MEV exposure.
MEV protection is not a guarantee against every loss. It does not make an unsafe token safe, prevent a user from signing a malicious approval or eliminate market movement. A user still needs to understand the minimum amount, expiry, partial-fill behaviour and the status of the submitted order.
Normal swap, Fusion order and limit order
- Aggregation swap: a wallet submits an onchain swap through the selected route and normally pays the applicable network cost.
- Fusion order: an intent is submitted and a resolver may execute it under the order conditions.
- Limit order: defines a target rate and expiry; it can remain unfilled, fill partially or expire.
Choose the mechanism because its execution rules fit the goal, not because one mode sounds automatically safer. Check the live interface for the conditions, fees and supported networks of the specific trade.
Approvals remain a separate risk
Aggregation does not remove token permissions. A first trade may request an allowance for a token. Verify the official domain, token, network, spender and amount before signing. Do not accept an unexplained approval simply because the quote looks attractive. Review unused approvals periodically and reduce or revoke permissions that are no longer needed through a trusted tool on the correct network.
Benefits and trade-offs at a glance
| Potential benefit | Important limit |
|---|---|
| Access to fragmented liquidity | Route quality changes with market conditions. |
| Possible lower price impact | Does not guarantee a good investment or liquid exit. |
| Fusion execution can reduce public-mempool exposure | Does not protect seed phrases, unsafe approvals or fake tokens. |
| Route comparison in one interface | User must still verify token contracts and total costs. |
| Self-custody execution | User bears wallet recovery and signature responsibility. |
Before confirming a 1inch trade
- Use a saved official 1inch address, not an advertisement or direct-message link.
- Verify the token contract and network from a primary official source.
- Review input, expected output, minimum received, route, gas and price impact.
- Understand whether the wallet request is an approval, signature, order or swap transaction.
- Use a small test amount for an unfamiliar token, network or route.
- Never enter a seed phrase or private key to connect a wallet.
Official 1inch resources
- 1inch — DEX aggregators explained — what aggregation does and how routing models differ.
- 1inch — How Fusion delivers MEV-protected swaps — resolvers and intent-based execution.
- 1inch — MEV-protected swaps — front-running and sandwich-risk overview.
- 1inch — Aggregation Protocol and Pathfinder — routing across liquidity sources.
Aggregation is useful when it helps a user compare fragmented liquidity with clear conditions. It is not a substitute for checking the token, permission and final transaction. The best route is meaningful only when the entire trade remains understandable and intentional.