Uncertainty regarding the implementation of the liquidity fee

So what's this then:


Again, we are left to guess what some of your code actually does.
In this case - an internal function in your contract, called addLiquidity.

Anyways, have you stopped at any point to read this part in one of my previous comments:


In other words, regardless of whether it is your swapAccumulatedTokensForEth function or your addLiquidity function which calls a function on the Uniswap Router contract, you still get to a point where that Uniswap Router contract function calls back your contract's _transfer function.

Please try to actually stop and think about it this time.

Your internal _transfer function should generally be very simple, handling token-transfer only, and not complex stuff like adding liquidity, etc.

1 Like