DCOREUM (DCO) - Audit

The total amount of the initial mint or `_totalSupply * 10 ** decimal()` tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute `_totalSupply * 10 ** decimal()` tokens without the consensus of the community. It is noted that the contract address of the `superAdminAddress` [0x6080b14E69157e8dcA7F28aB1CDbb48fd3777363](https://bscscan.com/address/0x6080b14E69157e8dcA7F28aB1CDbb48fd3777363) which the contracts from the initial mint are being sent to is a Gnosis Safe Proxy. Moreover, the Gnosis Safe Proxy only has one owner address: [0xD6Cf3A91A0ff9b7148D47E8Bd612508A811c07CF](https://bscscan.com/address/0xD6Cf3A91A0ff9b7148D47E8Bd612508A811c07CF).

In the contract `DCO` the role `owner` has authority over the functions shown in the diagram and list below: * `excludeFromFees()` - Exclude certain addresses from the deduction of fees on token transfers * `setLpAddress()` - Set liquidity pool address Any compromise to the `owner` account may allow the hacker to take advantage of this authority to set the `lpAddress` or exclude addresses from fees.  In the contract `OwnableContract` the role `owner` has authority over the functions shown in the diagram and list below: * `setOwner()` - Set a new `owner` address and revoke access of original `owner` * `renounceOwnership()` - Revoke `owner` access without setting a new `owner` address Any compromise to the `owner` account may allow the hacker to take advantage of this authority to set owner or renounce ownership.