So... after all this, the issue doesn't seem to be as bad as I thought, and it's really only some weird MEV shennanigans that was going on with the WETH-FXS route.
Conclusion
A very simple fix is swapping with the exact FXS -> FRAX path to make sure this doesn't happen again in the future
Issue
The most recent![image](https://user-images.githubusercontent.com/71284258/133681907-0d459b6a-04fc-402c-8f4a-b1fd9ca81b7e.png)
harvest
transaction for the Saddle D4 jar presents a couple problems. https://etherscan.io/tx/0x4a3f79b7a711add58dfdb641e784ea733207e79011f2cf37718bf6c98883e485. A summary of the swap is belowEach of the reward tokens are sold in the following manner:
_swapUniswap(fxs, frax, _fxs);
which trades with thepath
FXS -> WETH -> FRAXStep 1: reward token to ETH
Step 2: ETH to Stablecoin
So... after all this, the issue doesn't seem to be as bad as I thought, and it's really only some weird MEV shennanigans that was going on with the WETH-FXS route.
![image](https://user-images.githubusercontent.com/71284258/133684761-fd21823e-b3ce-4e75-8adc-4f1099e6e691.png)
Conclusion
A very simple fix is swapping with the exact FXS -> FRAX path to make sure this doesn't happen again in the future