Uncertainty regarding the implementation of the liquidity fee

[barakman]

So what's this then:

@Nikol

addLiquidity(liquidityFee, address(this).balance);

???

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:

@barakman

Inside function _transfer, you seem to be calling function addLiquidity in YOUR contract.

Again, you haven't provided the code of that function, but by name, I am inclined to guess that this function calls function addLiquidity on the Uniswap Router contract...?

If so, then what you get here is a kind of a recursive loop, starting as you add liquidity via the Uniswap web interface:

• Which calls function addLiquidity on the Uniswap Router contract
• Which calls function transferFrom on your contract
• Which calls function _transfer on your contract
• Which calls function addLiquidity on your contract
• Which calls function addLiquidity on the Uniswap Router contract

???

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.