I lost more on a DeFi Saver swap than I expected

After executing a transaction on DeFi Saver that includes swaps, such as:

  • Creating a leveraged position

  • Repay

  • Boost

  • Close

Based on the assets being swapped, you might think that you got a very bad price for one of the swaps on Etherscan. Let's look at an example:

  1. On the following Etherscan transaction, we can see a DeFi Saver "Leveraged Create" transaction:

Open screenshots:

  1. DeFi Saver meta-aggregates the most popular DEX aggregators in order to find the best posible swap price for users. It also finds the best flash loan option available, focusing on those that don't have fees.

  1. Within the Etherscan transaction, we can see the following swap:

  1. Seemingly, this transaction swapped 3,984,878 sUSDe worth $4,781,853.65 for 4,726,804 USDT, which is over a $50,000 loss on the swap. This might seem like a considerable loss and not aligned with the slippage settings at the time the transaction was submitted.

  1. However, the issue here is that the dollar values Etherscan shows is the current value of tokens on CoinGecko and CoinMarketCap - not the market price at the time of the swap.

  1. So if we take a look at the market price of the sUSDe/USDT pair on Fluid at the time of the transaction, it's going to show us the actual swap value:

Show me the breakdown:

The date and time of the Etherscan transaction:

The Fluid DEX chart for the sUSDe/USDT pair on that date and time:

This gives us the price of 1 sUSDe = 1.18709 USDT

Going back to the swap, we have: 3,984,878 sUSDe * 1.18709 = 4,730,409 USDT

This gives a loss of $3,605 which fits within slippage settings of 0.1% for such a large transaction.

We can now see how it might look like you lost more funds during a swap than expected.

This might not always be the case, as your transaction could be the victim of an MEV attack. To secure yourself from these and ensure you get the best swap prices, we recommend using TxSaver when submitting your transaction.

Last updated