Why Can a Fee-on-Transfer Token Break a Normal DEX Quote?

A fee-on-transfer token withholds part of an amount inside its own logic during a buy, sale, or ordinary transfer. A router may therefore send the quoted input while the pool actually receives less. A normal quote that ignores this behavior becomes inaccurate, increases slippage, or causes the transaction to revert.

Where does the difference arise?#

A router builds a path around an expected input. The fee-on-transfer contract sends the pool the amount minus a tax, while diverting the remainder to a treasury, burn, or redistribution mechanism. Reserves therefore change differently from the standard assumption.

Why does slippage increase?#

A user specifies minimum output. When actual input is lower, output falls and can violate that limit. Uniswap explains that the issuer defines the token fee and may apply it to buys, sells, or transfers.

How can this token type be checked?#

Review source code, current buy and sell tax, administrator powers, and recent transactions. A small test trade reveals current deductions but cannot prove the owner will not change settings later. The selected router must also support this transfer behavior.

What are the limits and risks?#

An administrator may raise tax, blacklist an address, or restrict selling when the contract allows it. High slippage does not fix a honeypot; it only widens acceptable loss. Thin liquidity adds market impact on top of the token’s internal fee.

What are the key takeaways?#

• The token contract, not necessarily the DEX, collects the fee.
• The pool prices against the amount it actually receives.
• A standard quote can overstate output.
• The tax may change after a purchase.
• Unusual transfer logic requires contract review.