1inch is a DEX aggregator that balances swap output against execution cost

1inch is a decentralized exchange aggregator: it compares token-trading pools and assembles a route that balances quoted output against execution cost. Pathfinder divides an order across liquidity sources, while Fusion converts the trade into a signed intent filled by competing resolvers. Users retain wallet control and compare the quoted output, price impact, infrastructure fee, and network cost before committing.

The central decision is operational: choose Classic for direct, configurable on-chain execution, Fusion for a gas-abstracted same-chain intent, or Fusion+ for an atomic cross-chain exchange. Each path shifts who submits transactions and where costs appear.

Bottom line: A split route wins only when its extra token output exceeds the gas and fee burden of added hops.

Fusion and Fusion+ move execution toward signed intents

Fusion and Fusion+ are notable because 1inch extends aggregation beyond a single router transaction, using signed orders and resolver competition for same-chain and cross-chain settlement.

Fusion encodes a maker's terms in EIP-712 typed data and broadcasts the order to resolvers. A Dutch auction moves from the desired exchange rate toward the signed minimum return until filling becomes economic. The resolver submits the on-chain transaction and pays gas, then prices that expense into the rate it is willing to fill. Fusion+ links two escrows with one secret hash. Its normal lifecycle has three phases - announcement, deposit, and withdrawal - with an optional fourth recovery phase after a timelock. The mechanism spans Ethereum, chain ID 1, and Solana, chain ID 501, among other documented networks.

Recovery follows the execution model, so a signed intent, an escrowed cross-chain order, and a restored wallet rely on different fixed mechanisms.

Uniswap, Curve, CoW Swap, and ParaSwap on the decision grid

Choose 1inch when route discovery across several venues matters; choose a direct pool or another solver model when its narrower workflow matches the trade. Uniswap gives direct pool interaction and exposes the pool's own fee and liquidity, while a Uniswap v2 pool charges 0.30% per swap. Curve concentrates liquidity around correlated assets. CoW Swap uses batch auctions and coincidence-of-wants matching, whereas ParaSwap also aggregates decentralized exchange liquidity. PancakeSwap is a direct automated market maker on BNB Chain and other networks. The deciding dimension is total destination-token output after pool fees, route complexity, execution cost, and fill conditions.

How does Pathfinder build a swap route?

Pathfinder builds a route by comparing executable liquidity, dividing volume where useful, and subtracting the gas burden of each candidate path from its expected token output.

A quote may traverse Uniswap, Curve, Balancer, or other supported liquidity sources, and a connector asset such as WETH can bridge otherwise separate pools inside one transaction. Every added hop offers another price opportunity and another contract call. Route parts add to 100%, yet the route with the highest raw output does not automatically win: more hops consume more gas. Pathfinder therefore optimizes the delivered amount rather than merely selecting the pool with the displayed price. Ethereum uses chain ID 1, BNB Chain uses 56, Polygon uses 137, Optimism uses 10, and Arbitrum uses 42161; routing never crosses these ledgers inside a Classic swap.

Classic execution sends one router transaction after any required allowance. Token precision also matters: the 1INCH token uses 18 decimals, so the router handles integers in the token's smallest unit rather than display-formatted amounts. The quote binds a source token, destination token, amount, chain, and recipient. If any of those inputs changes, request a fresh quote.

Preparing and executing a first swap

A first 1inch swap works cleanly when the wallet holds the source asset on the chosen network and the execution mode matches the task.

Start by connecting a self-custody wallet such as MetaMask, Ledger through a compatible connector, Coinbase Wallet, or Phantom for Solana. Match the wallet network to the asset balance before requesting a quote. Base identifies itself with chain ID 8453, while Avalanche uses 43114 and Gnosis uses 100. A token name alone cannot establish the correct asset because contracts on separate networks use different addresses. Select the source and destination tokens, enter the amount, and examine the minimum received alongside the route and fee lines. Then select Classic, Fusion, or Fusion+ based on settlement scope.

• Wallet network and source-token balance
• Exact destination-token contract and recipient
• Minimum received, price impact, and route
• Infrastructure fee and estimated network cost
• Approval amount, spender, and order expiry

ERC-20 assets require an allowance before a router can transfer them. A first Classic swap therefore uses two on-chain actions when no allowance exists: one approval and one swap. Native ETH skips the ERC-20 approval. EIP-2612 can replace a separate approval transaction for supporting tokens, while a previously authorized Permit2 flow uses a signature for a compatible swap.

Read the wallet prompt as the final execution sheet. Classic shows an on-chain call and network fee. Fusion shows typed order terms, including the minimum return and expiry, because a resolver later executes the trade. Fusion+ adds source and destination chains. Reject the prompt if its network, token amount, recipient, or spender differs from the reviewed quote.

After confirmation, record the transaction hash or order identifier. For Classic, inspect the chain receipt and destination-token balance; a successful receipt establishes execution, while the balance change shows delivery. For Fusion, follow the order status through filling or expiry. Fusion+ needs both source and destination settlement states, since its two escrows complete on separate ledgers. Wallet interfaces sometimes display a balance late even after settlement. Compare the address against the chain record before repeating an order, because a duplicate submission creates a new swap rather than refreshing the previous status.

Where the quote, gas, and token risks sit

The decisive 1inch trade-off is the gap between quoted destination tokens and the amount delivered after liquidity fees, infrastructure fees, price movement, and execution cost.

Classic exposes network gas directly to the sender. Pool fees remain inside the route economics, and each hop increases execution work. The 1inch interface fee range is 0-5 basis points for stable pairs and 0-30 basis points for non-stable pairs; one basis point equals 0.01%. Fusion presents resolver-paid gas as part of the auction economics, so "gasless" means no separate gas payment from the maker, not zero execution cost. A wider minimum-return tolerance improves execution probability but permits a lower received amount. A tight threshold protects the floor and raises the chance of a reverted Classic transaction or an unfilled intent. The other half of this is described in 1inch tutorial.

Token behavior adds another layer. Fee-on-transfer tokens reduce the amount reaching a route, rebasing tokens alter balances outside ordinary transfers, and shallow pools amplify price impact. The Classic API accepts either a slippage percentage or a minimum return and bounds its slippage parameter from 0% through 50%; that integration limit is not a sensible default. Use the smallest tolerance that still reflects the pair's depth and expected confirmation delay, which is discussed in 1inch 101.

The 1INCH governance and utility token is separate from the swap service. Its total issuance is 1.5 billion units, its ERC-20 representation uses 18 decimals, and users do not need it to request ordinary swap quotes. Token value, resolver economics, and governance participation are distinct decisions. Mixing them obscures the cost of the actual trade.

Does 1inch fit your operating workflow?

1inch fits a workflow that values quote comparison and flexible execution, provided the operator verifies chain, token contract, minimum return, and settlement status at each stage. Routine same-chain swaps suit Fusion when signed intents and resolver execution are acceptable. Classic suits applications that need immediate calldata, explicit slippage controls, or selected protocols. Fusion+ covers atomic exchanges between supported networks without a conventional bridge transaction. Direct Uniswap or Curve interaction stays simpler when one known pool already gives the preferred route, while CoW Swap offers a different batch-auction model. Requote after material market movement, review allowances during maintenance, and archive identifiers for reconciliation.

Before you start with 1inch