NFE - Audit

In the contract `NonFungibleEstate` the role `_owner` has authority over the functions shown in the diagram below. - `transferOwner` : Change the `_owner` to a new specify address. - `renounceOwnership` : Change the address of `_owner` to zero. - `approveContractContingency` : Set the maximal allowance for this contract to `dexRouter`. - `setNewRouter` : Change the `dexRouter` address. - `setLpPair`: Set the liquidity pool pair of the contract. - `setInitializer` : Set the `Protections` address Contract. - `setExcludedFromFees`: Exclude a specific address from the fees. - `setExcludedFromProtection`: Exclude a specific address from the protections. - `removeSniper` : Call the `removeSniper` function of the `Protections` contract with a specific address. - `setProtectionSettings`: Call the `setProtections` function of the `Protections` contract. - `lockTaxes`: Lock the current tax rates forever. - `setTaxes` : Set the taxes amount. - `setRatios`: Set the amount of the ratios. - `setWallets`: Set the addresses of `marketing` and `development`. - `setSwapSettings`: Set the `swapThreshold`. - `setPriceImpactSwapAmount` : Set the price impact amount. - `setContractSwapEnabled`: Enable/Disable the swapping of the token. - `excludePresaleAddresses`: Exclude a specific address from the fees. - `enableTrading` : Enable the trading. - `sweepContingency`: Withdraw the native token from the contract. - `multiSendTokens`: Send to multiple addresses. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and pause the swapping or set an arbitrary address for the `Protections` contract. In the contract `NonFungibleEstate` the role `originalDeployer` has authority over the functions shown in the diagram below. - `setOperator`: Set a new Operator. - `renounceOriginalDeployer`: Set `originalDeployer` to address(0). Any compromise to the `originalDeployer` account may allow the hacker to take advantage of this authority and set an arbitrary operator. There are two fee collectors, i.e. `marketing`, and `development`, over time, these accounts would gain many fees. Any compromise to the `marketing`, and `development` accounts may allow the hacker to take advantage of this authority.

All of the `NFE `tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute tokens without obtaining the consensus of the community. ```solidity=188 _tOwned[_owner] = _tTotal; ```