When a Rebase Stalls Your Swap, Check the Order State First

If a rebase stalls your swap, first find out whether the swap was submitted on-chain or is still a signed order waiting for execution. A rebase changes token balances by changing supply, often without a transfer into or out of your wallet. That can leave a displayed balance, quote, or order amount out of step with the token contract’s current accounting. It does not, by itself, prove that a transaction is stuck.

Before rebasing tokens became a concern, a wallet balance and the amount shown in a fresh quote usually changed only after a transfer or another visible transaction. Rebasing tokens complicate that picture: balances can move as a result of the token’s supply rules. The practical distinction is between a stale display and a failed execution. The cowswap explainer covers the order flow in more detail; here, the key is to identify which stage has stopped.

Why can a rebase interrupt a swap?

A rebase changes how many units each holder owns, or how the contract calculates those units, while changing the token’s total supply. The trigger and timing depend on the token. Some update balances automatically; others apply changes at set times or after a separate action. A wallet may therefore show a different sell balance even though you did not send or receive tokens.

A swap quote assumes the sell amount and expected proceeds can be executed under the token’s current rules. If the balance changes between quoting and execution, the order may exceed the amount available, fall outside its allowed price limits, or fail a token or pool compatibility check. The exact result depends on the token, the swap route, and the trading system. A rebase does not guarantee failure, and a failed swap does not establish that a rebase caused it.

There is another distinction: a swap interface can use off-chain orders that are settled later, while a direct swap typically submits a transaction for on-chain execution. A signed order may remain pending even when there is no pending transaction in your wallet. A submitted transaction may instead be waiting for the network to include it in a block. Those are different problems with different remedies.

How do you tell whether the swap is actually stuck?

Check the activity record in the swap interface and your wallet before changing anything. Look for an order status, a transaction hash, and whether the sell token was transferred. Then check the wallet’s current token balance using a trusted wallet or block explorer view. If the displayed balance differs from the balance the swap interface used, refresh the token data and request a new quote before signing another order.

Use these checks to narrow down the cause:

• No transaction hash and an order marked pending: the order may be waiting for a match or settlement. Review the order’s expiry and cancellation options.
• A transaction hash with no confirmation: check its status on the relevant chain. This is a network transaction delay, not simply a stale quote.
• A failed or reverted transaction: read the failure details if available. A changed balance, token behavior, price limit, or unsupported asset may be relevant.
• No order and no transaction: the wallet may not have completed the signature or submission. Recheck the interface state before starting again.

Do not submit the same swap repeatedly while the original order or transaction may still execute. If an order is live, cancel it through the interface and confirm the cancellation state before placing a replacement. For on-chain transactions, a replacement transaction or cancellation can have chain-specific effects; check the wallet’s nonce and transaction status first. A displayed “cancelled” request may not mean an order was already prevented from settling.

Should you retry, change route, or avoid the token?

Retry with a fresh quote only after confirming the earlier order is cancelled, expired, failed, or otherwise unable to execute. Verify the sell amount against the token’s current balance, then review the minimum amount you will receive and any price tolerance before signing. A larger tolerance may make execution more likely when prices move, but it also permits a worse price; it does not fix incompatible token accounting.

Changing the route can help if the first route relies on a pool or router that handles the token poorly. It cannot make every rebase token compatible. For example, Uniswap’s documentation warns that rebasing tokens can create accounting problems for liquidity providers in its v3 pools. That is a pool-level trade-off, separate from whether a wallet can display a balance or a swap interface can form an order.

If a token repeatedly causes stale balances, failed transfers, or confusing settlement states, the safer choice for most readers is to pause and verify its rebase schedule and compatibility before trading it again. A standard token may offer a simpler route, but compare the actual market depth and price rather than assuming a familiar asset will produce a better trade. The decision is about execution certainty as well as quoted price.

What should you watch after the swap?

After a successful swap, check both the transaction or order’s final status and the received token balance. A rebase may later change that balance without changing the amount originally settled. Keep the transaction record so you can distinguish the swap’s execution from subsequent supply changes.

The useful signals are the order’s expiry or cancellation state, the on-chain transaction status, the token’s current balance, and whether fresh quotes continue to fail for the same route. If the order completed and the balance later moved, investigate the token’s rebase mechanics. If execution failed, use the failure details and route behavior to decide whether a fresh quote is reasonable or the token should be left alone.