Why Some Tokens Break a Direct Swap

A direct swap can fail when a token’s transfer rules differ from what its route expects. That matters because a quote assumes the tokens can move between your wallet and a pool in the usual way. A fee, transfer limit or blocked address can change that movement.

A direct route trades through one pool, while a routed trade passes through several. For a fuller guide to choosing between them, see fermi swap. The key detail is that every pool hop requires token transfers, and the token’s contract sets the rules for those transfers.

How can token rules stop a direct swap?

A direct swap can stop if the token contract rejects a transfer or delivers less than the route expects. Under the ERC-20 interface, a transfer moves a stated amount from one account to another. But token contracts can add rules around that movement.

A token may charge a fee on transfer, restrict transfers to certain addresses, or pause transfers altogether. If the contract blocks a transfer from your wallet to the pool, the transaction reverts. If it allows the transfer but takes a fee, the pool may receive less than the amount shown in the quote. A price-impact or slippage setting cannot override a transfer rule enforced by the token.

Why does a token fee affect the route?

A transfer fee changes the amount that reaches the pool, so the output may differ from the route’s estimate. A pool calculates its swap using the amount it receives. Some routers have methods designed to support fee-on-transfer tokens for exact-input swaps, where the user sets how much to send and accepts a minimum output. Support depends on the router and route.

Exact-output swaps are harder to support with transfer fees. They start with a chosen amount to receive and calculate how much input is needed. If a fee reduces the amount that arrives at each step, that calculation may no longer hold. With multiple pools, an intermediate token has to move from one pool to the next, so a restriction or fee can affect more than one transfer.

What should you check before trading?

Check the token’s transfer rules and whether the route supports them. The contract code and project documentation can reveal fees, address limits or pause controls; the swap quote alone cannot. Before confirming, look for:

• The amount you will send and the minimum amount you can receive.
• Whether the token charges a fee when sent to a pool or another address.
• Whether the route’s router supports that token behavior.
• Whether transfers are limited, paused or blocked for certain addresses.

Rebasing tokens—whose balances can change without a transfer—can also confuse systems that expect balances to change only when tokens move. A direct route uses fewer steps, which can reduce places for a restriction to bite, but it cannot make a blocked or paused transfer work. For most readers, the better route is the one whose router supports the token’s rules and whose minimum output they are willing to accept.