ADreward(AD)

Inside of the constructor in `TokenERC20`, `totalSupply` is calculated without SafeMath. The lack of SafeMath can allow for arithmetic overflow. As such the current calculation of `totalSupply` can overflow if the input from `initialSupply` is unusually high.

In the contract `TokenERC20`, the requirement check that balanceOf[_to] + _value > balanceOf[_to] disallows transfers of value 0. This could create incompatibility with third parties protocols. However, the check inside of `EGAMEAD` will pass on zero transfers.

The ERC-20 `approve` function has a well-known race condition whereby an adjustment of an existing approval can be exploited to utilize the full amount of the previously set approval, as well as the newly set approval by monitoring the transaction mempool. See also [ERC20 API: An Attack Vector on Approve/TransferFrom Methods](https://docs.google.com/document/d/1YLPtQxZu1UAvO9cZ1O2RPXBbT0mooh4DYKjA_jp-RLM/edit#heading=h.m9fhqynw2xvt).

The function `release()` and modifier `OnlyReleased()` would be better described as `togglePause()` for the function and `whenNotPaused()` for the modifier.

Functions that affect the status of sensitive variables should be able to emit events as notifications to customers: - `release()`. - `transferOwnership()`. - `approveandCall()`. Additionally, since the `owner` is updated on deploy, the `constructor` should emit an event of this occurrence.

The following modifiers and functions should emit an error message in the require statement: Modifiers: - `onlyReleased()`. - `onlyOwner()`. ------- Functions: - `transferFrom()` - `release()`. - `_transfer()`. - `approve()`. - `burn()`. - `burnFrom()`.

The function `transferOwnership()` should check if the `newOwner` is not the zero address. If this function is intended to send ownership to the zero address, then the functionality should be separated.

The `assert` function should only be used to test for internal errors, and to check invariants. The `require` function should be used to ensure valid conditions, such as inputs, or contract state variables are met, or to validate return values from calls to external contracts.

In the function `release()`, it checks if the `msg.sender` is the owner. However, this is already checked inside of `OnlyOwner`.

The `_transfer()` function in `EGAMEAD` is almost identical to the `_transfer()` inside of `TokenERC20` except for the following checks: ```solidity=110 assert(balanceOf[_from].add(balanceOf[_to]) == previousBalances); ``` ```solidity=211 require(!frozenAccount[_from]); // Check if sender is frozen require(!frozenAccount[_to]); // Check if recipient is frozen ``` Instead of reusing the code, `super._transfer()` can be used to access the remaining logic from `TokenERC20`.