PEPEDEX-Audit

Functions that update state variables should emit relevant events as notifications. The following functions do not emit any event: - `setNoFeeWallet`

Addresses are not validated before assignment or external calls, potentially allowing the use of zero addresses and leading to unexpected behavior or vulnerabilities. For example, transferring tokens to a zero address can result in a permanent loss of those tokens. ```solidity=330 marketingAddress = payable(marketing); ``` - `marketing` is not zero-checked before being used.

The contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assumes their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=177 IRouter02 public swapRouter; ``` - The contract `PEPEDEX` interacts with third party contract via `swapRouter`, as well as its related factory and LP pair.

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage. Note that the function `changeLpPair()` only updates the `isLpPair` mapping, but not the `lpPair` address declared in line 182.