Kuku - Audit

In the contract `KuKu` the role `_owner` has authority over the functions shown in the diagram and list below. * enableTrading() - Enable transfer of tokens for all users * changeLpPair() - Set a new address as an LP pair address * setNoFeeWallet() - Set address fee exemption status * setPresaleAddress() - Allow an address to participate in the presale * toggleCanSwapFees() - Set flag to allow/prevent swapping of tokens for native tokens * changeWallets() - Set new marketing wallets * transferOwnership() - Transfer contract ownership to another address * renounceOwnership() - Give up contract ownership Any compromise to the `_owner` account may allow the hacker to take advantage of this authority to set important contract parameters such as fee exemptions, fee wallets, and swap parameters.  

The function `changeLpPair()` has a misleading name that seems to change the current pair set in the `isLpPair` mapping. The function simply adds a new address to the `isLpPair` mapping, which would cause the newly added address to be subject to buy or sell fees in token transactions. The audit team would like to understand if the intended design is to support fees for multiple LP pair addresses. The audit team would also like to understand how the team intends to ensure that no addresses are incorrectly added to the `isLpPair` list since there is no mechanism to remove addresses from the mapping.