What happens to a stablecoin swap when the peg breaks during the transaction

05 September 2026

The swap executes at the market rate that exists the moment the transaction is confirmed, regardless of the peg. If the stablecoin has lost its peg by the time the block is finalised, you receive the broken-peg value, not the intended one-dollar equivalent.

Here is why that happens, and why it matters.

A swap is not a single atomic event from your perspective. It is a sequence. You submit an order. The exchanger finds a route or a liquidity pool. The transaction is broadcast to the blockchain. Miners or validators include it in a block. The block is finalised. Only at finalisation does the exchange rate lock.

The stablecoin's peg can break at any point in that sequence. The most dangerous window is the time between submission and finalisation. On a congested network this can be seconds; on some chains it can be minutes. The price feed that the exchanger uses updates continuously. If the stablecoin drops to $0.90 during that window, the swap will execute against the $0.90 price.

Two mechanisms protect you partially, but neither is a guarantee.

Slippage tolerance. When you set a swap, you can specify a maximum acceptable deviation from the quoted rate. If the peg breaks beyond that tolerance, the transaction reverts. You pay the network fee for a failed transaction, but you do not complete the swap at a bad rate. The problem: slippage tolerance is a blunt tool. A slow, gradual depeg of 2% might fall within your tolerance and still result in a loss. A sudden crash to $0.50 will trigger a revert, but you are then stuck holding the original asset while the peg continues to fall.

Oracle-based pricing. Some protocols use external price oracles to detect depegs and temporarily halt trading. This is not standard across all exchangers. The ones that use oracles can have a lag of several minutes. A fast depeg can outrun the oracle update. The moment the oracle finally reports the new price, the swap may already have gone through at the old, wrong price.

What happens to the other side of the trade? If you swapped USDC for USDT and USDC depegs, you receive fewer USDT than expected. If you swapped USDT for USDC and USDC depegs, you receive the full amount of devalued USDC. The loss lands on whichever side of the trade holds the broken asset.

The same logic applies to cross-chain swaps. If you send a stablecoin from Ethereum to Solana, and the peg breaks on Ethereum before the bridging transaction finalises, the receiving chain's wrapped version of that stablecoin will reflect the broken value. The bridge does not smooth the peg; it passes through the market price of the underlying asset.

There is no way to undo a confirmed swap. Reversing it would require a second swap at the new, worse rate. That is a separate transaction, subject to the same risks.

The practical takeaway: stablecoin swaps are not risk-free because the peg is not risk-free. A swap that looks safe at submission can become a loss by confirmation. The only control you have is to set tight slippage limits, monitor network congestion, and avoid swapping during periods of known market stress.

If you need to understand the broader context of moving between stablecoins and volatile assets, read the hub page titled "Swapping into and out of stablecoins". It covers the mechanics and risks of the full round trip, not just the stablecoin-to-stablecoin case.

Back to airdrops