AI Society - Audit

In the contract `HasMinters` 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 change the configuration of minter.  In the contract `IAISocietyToken` the role `minter` has authority over the functions shown in the diagram below. Any compromise to the `minter` account may allow the hacker to take advantage of this authority and mint current tokens.  In the contract `IAISocietyToken` 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, change the `_maxSupply` and prevent the token transfer.  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 change the ownership. 

All of the `AIS` 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.

In the contract `AIS`, the role `_owner` has authority to update the status of the `_paused` and further pause/resume the functionality of the `transfer()` and `transferFrom()` functions. Any compromise to the private key of the `_owner` may allow hackers to take advantage of this authority and allow/prevent external user access to the sensitive functionalities controlled by the `_paused`.