XODEX

The `set_New_Router_and_Make_Pair()`, `set_New_Router_Address()`, and `set_New_Pair_Address()` functions allow the contract owner to update either the pair contract or the router contract. Neither `set_New_Router_and_Make_Pair()` nor `set_New_Router_Address()` check if the pair has been created. If the pair has already been created, then calling `set_New_Router_and_Make_Pair()` on the factory contract will cause this function to revert. It would not be possible to update the router to this address with `set_New_Router_and_Make_Pair()` function. In addition, if the `set_New_Pair_Address` contract is set to an invalid pair then this would cause a denial of service when transferring tokens if the `swapTokens` functions is called.

The process_Tokens allows the `owner` to swap XODEX Tokens for BNB. However, consider the following lines of code within the function. ```solidity if (percent_Of_Tokens_To_Process > 100) { percent_Of_Tokens_To_Process == 100; } ``` The equality symbol `==` is incorrectly called.

The XODEX contract has three functions that enable the contract owner to update certain parameters: set_Number_Of_Transactions_Before_Liquify_Trigger, set_Max_TX_Percent, and set_Max_Wal_Percent. The set_Number_Of_Transactions_Before_Liquify_Trigger function allows the owner to update the maximum number of transactions that can occur before triggering a liquidity swap. The set_Max_TX_Percent function enables the owner to update the maximum percentage of tokens that can be transferred in a single transaction. Finally, the set_Max_Wal_Percent function allows the owner to update the maximum percentage of tokens that can be held by any single wallet.

The `_TotalFee` initially equals `_buyFee + _sellFee`. When a user tries to buy or sell tokens, it is assigned to either `_buyFee` or `_sellFee`. However, the `_TotalFee` is not recovered after the buy or sell transaction.

Addresses should be checked before assignment or external call to make sure they are not zero addresses. The following functions do not have a zero address check: 1. `Update__Dev_Wallet` 2. `excludeFromFee` 3. `includeInFee` 4. `set_New_Router_and_Make_Pair` 5. `set_New_Router_Address` 6. `set_New_Pair_Address` 7. `recover_Tokens` 8. `process_Tokens`

The `_transfer` includes the following logical statement: ```solidity require(from != address(0) && to != address(0), "ERR: Using 0 address!"); require(amount > 0, "Token value must be higher than zero."); ``` Moving the zero address check and zero transfer check to the beginning of the `_transfer` function can save gas by quickly eliminating obvious cases.

The following state variables are never updated within the contract: 1. `_name` 2. `_symbol` 3. `_decimals` 4. `_tTotal` 5. `Burn_Wallet` 6. `maxFee` Variables that that never change should be declared as `constant` to save gas.

The variable `_prevMaxToken` and the variable `_prevMaxTxAmount` are never used in within the `XODEX` contract.