1inch

1inch withdrawals are self-Custody Transfers Without Exchange Payout Queues

Last updated: 2026-08-10

1inch withdrawals are self-custody wallet transfers of tokens already settled to your address after a swap. 1inch doesn’t hold a customer balance or approve a payout, so there is no exchange queue to clear. You choose the destination, retain enough native gas for the sending network when required, and match the recipient’s chain and token contract.

That distinction shifts the decision from withdrawal policy to transaction construction. The important checks are custody, network identity, gas, token standard, recipient support, and on-chain confirmation before the funds move.

Fusion and Fusion+ expand direct settlement beyond Classic Swap

1inch withdrawals settle outside exchange payout queues because swap proceeds move into a user-controlled wallet through Classic Swap, Fusion, or Fusion+.

Classic Swap executes an on-chain transaction through the Aggregation Router, while Fusion uses a signed order filled by competing resolvers. Fusion+ extends the intent model across supported chains with paired escrow contracts. In each case, the destination balance is recorded on a blockchain rather than in a 1inch customer account. Once settlement completes, moving the asset again is a wallet send, not a release request. MetaMask, 1inch Wallet, Ledger-connected wallets, Coinbase Wallet, and WalletConnect-compatible clients expose that balance through the keys or account controls they manage. The interface isn’t holding a pending cashout behind an internal review step.

The absence of a payout queue removes platform processing time. Blockchain settlement, recipient rules, and network fees remain part of the transfer.

Set the destination before moving the proceeds

A clean onward transfer starts by fixing the receiving asset, network, and address before the 1inch swap or wallet send.

Five concrete conditions determine whether the transfer is ready.

• Match the recipient’s network to the chain holding the proceeds.
• Match the token contract or Solana mint, not merely its ticker.
• Use a destination controlled by you or issued for that exact deposit.
• Retain the network’s native asset when the wallet must pay gas.
• Use a permitted test amount when a new recipient has a deposit minimum.

Same-chain proceeds

A same-chain transfer is the shortest route because the asset stays on one ledger and needs no bridge or cross-chain order.

When USDC lands in MetaMask on Base and the recipient accepts native USDC on Base, the onward move is one token transfer after the swap. Base uses chain ID 8453, and its gas asset is ETH; the wallet therefore needs ETH on Base, not ETH held on Ethereum mainnet. Sending the same ticker over Arbitrum One changes both the chain context and the token contract. An identical 42-character address doesn’t make those routes interchangeable because EVM chains maintain separate ledgers and transaction histories.

Cross-chain destinations

A cross-chain destination calls for Fusion+ or a separate bridge before the final send. Fusion+ quotes a source asset, destination asset, source chain, destination chain, and receiver as one intent. A normal wallet transfer doesn’t cross chains by itself. If the destination is a centralized exchange, use the network named in its deposit instruction because a supported ticker on one chain doesn’t imply support for every representation.

Network identity matters as much as the wallet address

Additional context appears in 1inch questions. Network identity decides whether the destination can recognize a token, even when two EVM addresses display the same 42 characters.

An EVM account address contains a 20-byte value, written as 40 hexadecimal characters after the 2-character 0x prefix. Ethereum uses chain ID 1, Optimism uses 10, BNB Smart Chain uses 56, Gnosis Chain uses 100, and Polygon PoS uses 137. Base uses 8453, Arbitrum One uses 42161, and Avalanche C-Chain uses 43114.

Those chain IDs belong to the signed transaction context. An ETH balance on Ethereum is separate from ETH on Base, Arbitrum One, or Optimism, even when one private key controls the same EVM address across all four networks.

Solana follows a different account model. Its account keys are 32 bytes and are commonly displayed as 32-to-44-character base58 strings. Phantom therefore supplies a Solana destination rather than the 42-character EVM address used by MetaMask. Fusion+ may connect the two environments, while an ordinary send remains confined to its source chain.

Do 1inch withdrawals require a separate platform request?

Next to that, 1inch withdrawals require zero separate platform requests because the protocol doesn’t maintain an exchange-style balance awaiting release. With Classic Swap, an ERC-20 token lacking allowance commonly requires 2 transactions: approval and swap. Sending the proceeds afterward creates a third transaction. An existing sufficient allowance removes the approval step, while Fusion uses a signed order and resolvers execute settlement. The separate wallet send remains a new on-chain action rather than a 1inch account request.

Gas belongs to the send transaction

The onward wallet send pays the fee rules of its chain, independently of the route 1inch used for settlement.

EVM gas accounting

Ethereum-compatible transfers multiply gas used by the effective gas price, with the fee paid in the chain’s native asset. ETH pays on Ethereum, Base, Arbitrum One, and Optimism; BNB pays on BNB Smart Chain, POL pays on Polygon PoS, and AVAX pays on Avalanche C-Chain.

A plain Ethereum ETH transfer has an intrinsic cost of 21 000 gas, before optional data or access-list costs. ERC-20 transfers execute contract code and consume more gas. Under EIP-1559, a transaction specifies a maximum fee and priority fee, while the protocol supplies the block’s base fee. A full block raises the next base fee by no more than 12.5%. One ETH contains 10 ¹⁸ wei, so wallets convert gas prices from small denominations before presenting the charge.

Solana fee accounting

Solana charges a base fee of 5 000 lamports per signature plus an optional prioritization fee. One SOL contains 1 000 000 000 lamports. Its default compute budget is 200 000 compute units per non-builtin instruction, and a transaction can request no more than 1 400 000 compute units.

Fusion shifts the swap’s execution gas to resolvers, so the maker doesn’t submit the normal settlement transaction. A later wallet send has its own fee because it is a separate instruction from the completed order. Keeping native gas at the destination matters when the proceeds will move again, even if the preceding swap appeared gasless.

Token standards define what the recipient receives

The recipient receives a specific token contract or mint, so a familiar ticker never establishes compatibility by itself.

ERC-20 defines 6 core methods for balances, transfers, supply, and allowances, alongside the Transfer and Approval events. Decimals belong to each token contract rather than to the standard’s fixed requirements. Ethereum USDC uses 6 decimals, while DAI and WETH use 18. One WETH represents 1 ETH, but WETH is an ERC-20 token and ETH is Ethereum’s native asset; deposit systems may treat those assets separately (compare 1inch app ).

Solana uses SPL Token accounts and mints instead of ERC-20 contracts. A wallet receiving an SPL token needs an associated token account for that mint, which a transfer flow may create when absent. Token-2022 adds extensions to Solana’s token model, so the receiving application must support the actual token program as well as the visible symbol.

Confirmation replaces a payout status page

On-chain confirmation, not a 1inch payout status, proves the swap proceeds or onward transfer reached the destination.

An EVM transaction hash is 32 bytes, displayed as 64 hexadecimal characters plus the 0x prefix. Once the transfer has 1 confirmation, it has entered a block and can’t be replaced through its nonce. A recipient may require additional confirmations before crediting a deposit, since that threshold belongs to the receiving service rather than the 1inch protocol.

Check the destination balance, token Transfer event, transaction status, and chain ID together. Etherscan covers Ethereum, while chain-specific explorers expose Base, Arbitrum One, Optimism, Polygon PoS, and other ledgers. This on-chain record is more informative than a pending exchange queue, although a custodial recipient can apply a later internal crediting step.

Direct wallet settlement and exchange withdrawals serve different jobs

Self-custody settlement suits immediate wallet control, while an exchange withdrawal serves assets already recorded inside a custodial account.

Coinbase and Kraken maintain internal customer balances before broadcasting approved withdrawals. Their withdrawal charge, supported networks, deposit minimums, and confirmation thresholds are venue policies. With 1inch, the protocol doesn’t set an onward withdrawal fee; the sending chain charges the wallet transaction. A direct deposit from a swap can also arrive through a smart-contract transfer, so the receiving venue’s crediting system must recognize the event type.

Uniswap and PancakeSwap resemble 1inch in this custody decision because their swaps also settle on-chain to a wallet. Their routing differs: 1inch aggregates liquidity across sources, while each individual decentralized exchange primarily exposes its own liquidity system. Changing from 1inch to another decentralized exchange therefore changes route selection, not the wallet-controlled settlement model offered by a custodial venue.

The route finishes where custody begins

The withdrawal-like experience follows from three settlement paths, each ending with assets under the receiver’s wallet control.

Classic Swap routing

Classic Swap submits a transaction to the 1inch Aggregation Router, which may divide execution across liquidity sources such as Uniswap and PancakeSwap. The router transfers the output token to the configured receiver during execution. If the receiver is the connected wallet, no later withdrawal from 1inch exists; the wallet balance is already the settled output.

Fusion order settlement

Fusion turns the trade into a signed intent. Resolvers compete to fill the order and pay the on-chain execution gas, while the user receives the quoted output under the order’s conditions. The signature authorizes settlement without handing 1inch custody of an account balance. Once filled, the asset sits at the receiver address and follows that chain’s normal transfer rules.

Fusion+ cross-chain settlement

Fusion+ coordinates 2 chains through source and destination escrows, a Dutch auction, and a cryptographic secret. Its hash lock uses a 32-byte value, and revealing the secret completes the paired settlement path. Partial fills use Merkle proofs when an order is divided. The mechanism replaces a manual swap-then-bridge sequence for supported pairs, yet the final asset still arrives under the destination chain’s token rules. From that point, another movement is a wallet send rather than an exchange withdrawal request.