Fee on transfer tokens will be able to perform swaps because there is no additional slippage that the user can set. The protocol has stated that they intend to support a Fee on transfer token such as PAXG
.
Fee on transfer tokens will not be able to be swapped with the current implementation, due to the fact there is no additional slippage that allows for a lower return in amountOutMinimum
, or the implementation of the router function swapExactTokensForTokensSupportingFeeOnTransferTokens()
that supports fee on transfer token swaps.
We can see in the function calculateMinimumAmountOut()
gets the exact value of amountOutMinimum
required to perform the swap without any slippage.
The protocol has stated that they intend to support a Fee on transfer token such as PAXG
. A fee on transfer token will have a high chance of failing during swap because there is no slippage calculation done, or the implementation of the router function swapExactTokensForTokensSupportingFeeOnTransferTokens()
. This will result in a user not being able to swap their assets, and could be potentially liquidated during a high volatile period.
Manual Review
To solve this issue, the calculateMinimumAmountOut()
function could take into account of a user's slippage and risk tolerance for the swap. Or they could implement the function swapExactTokensForTokensSupportingFeeOnTransferTokens()
that will check the recipient amount rather than the sending amount when calculating the invariant
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.