DIGIKA - Audit

In the contract `DGKToken`, the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and set address fee exemption status, set or unset a minter status, remove an address from the blacklist, set the transaction fee, set the paused state, set the treasury wallet address, set the transaction cooldown, blacklist an address, and mint tokens to a specified address.  In the contract `DGKToken`, the role `isMinter` has authority over the functions shown in the diagram below. Any compromise to the `isMinter` account may allow the hacker to take advantage of this authority and mint tokens to a specified address.  In the contract `Lock`, the role `owner` has authority over the functions shown in the diagram below. Any compromise to the `owner` account may allow the hacker to take advantage of this authority and withdraw the contract balance if conditions are met.  In the contract `Ownable`, the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and renounce the current ownership or transfer ownership to a new owner. 

Half of the max supply `DGK` tokens are sent to the contract deployer or one or several externally-owned account (EOA) addresses. This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.