Rebasing tokens and failed swaps: check router compatibility

Rebasing changes token balances according to the token’s rules, which can conflict with assumptions in a router or pool. Whether a particular swap works depends on the token and route; “all rebasing swaps fail” is too broad.

Separate swap support from pool risk

Uniswap’s v3 technical guidance makes a useful distinction: it describes rebasing-token concerns and notes that swaps can occur while active liquidity providers bear negative-rebase losses. A route being technically executable does not establish that every integration handles the asset safely.

For a user troubleshooting a swap, identify the exact router version and token contract. Do not rely solely on a generic help article’s category label.

Check the state used by the quote

A displayed wallet balance can change without an ordinary transfer from your account. Compare the current onchain balance with the requested input. If the application retained an earlier amount, refresh it and obtain a new quote.

Also check for other nonstandard features, such as transfer deductions or restrictions. “Rebasing” may not be the only relevant behavior.

If simulation still fails, ask the application whether it supports this contract through this route. Repeatedly raising gas or approval cannot correct an unsupported accounting model. If a swap succeeds, reconcile actual balances and receipt evidence rather than assuming the old wallet display remains the correct reference.

This diagnosis concerns execution compatibility. It does not evaluate the token’s economic design or recommend holding it.