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.

![](https://accelerator-tasks-prod.s3.amazonaws.com/aa55266128b94cdfa8c8bb6c53e78102/diagrams/centralization-Ownable-_owner.svg)

Centralization Risk in StandardToken.sol

All of the specified tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute the specified tokens without obtaining the consensus of the community.

Initial Token Distribution

Addresses should be checked before assignment or external call to make sure they are not zero addresses.\
The constructor function will fail if the `serviceFee_` is bigger than msg.value. \
If the msg.value is bigger than `serviceFee_`, the remaining native tokens will be locked in current contract, it's better to make sure msg.value equals to `serviceFee_`.

File: projects/FGD/contracts/StandardToken.sol (Line 216, Function `StandardToken.constructor`)
```solidity
        payable(serviceFeeReceiver_).transfer(serviceFee_);
```
- `serviceFeeReceiver_` is not zero-checked before being used.
- `serviceFee_` is not checked to be compared with msg.value before being used.



Missing Validation

The functions which are never called internally within the contract should have external visibility for gas optimization.

File: projects/FGD/contracts/StandardToken.sol (Line 172, Contract `Ownable`)
```solidity
    function renounceOwnership() public virtual onlyOwner 
```


---
File: projects/FGD/contracts/StandardToken.sol (Line 176, Contract `Ownable`)
```solidity
    function transferOwnership(address newOwner) public virtual onlyOwner 
```


---
File: projects/FGD/contracts/StandardToken.sol (Line 245, Contract `StandardToken`)
```solidity
    function transfer(address recipient, uint256 amount)
        public
        virtual
        override
        returns (bool)
```


---
File: projects/FGD/contracts/StandardToken.sol (Line 265, Contract `StandardToken`)
```solidity
    function approve(address spender, uint256 amount)
        public
        virtual
        override
        returns (bool)
```


---
File: projects/FGD/contracts/StandardToken.sol (Line 275, Contract `StandardToken`)
```solidity
    function transferFrom(
        address sender,
        address recipient,
        uint256 amount
    ) public virtual override returns (bool)
```


---
File: projects/FGD/contracts/StandardToken.sol (Line 292, Contract `StandardToken`)
```solidity
    function increaseAllowance(address spender, uint256 addedValue)
        public
        virtual
        returns (bool)
```


---
File: projects/FGD/contracts/StandardToken.sol (Line 305, Contract `StandardToken`)
```solidity
    function decreaseAllowance(address spender, uint256 subtractedValue)
        public
        virtual
        returns (bool)
```



Function Should Be Declared External

Similar names make the code more difficult to review.

`_totalSupply` is too similar to `totalSupply_`.

File: projects/FGD/contracts/StandardToken.sol (Line 199, Contract `StandardToken`)
```solidity
    uint256 private _totalSupply;
```

File: projects/FGD/contracts/StandardToken.sol (Line 205, Function `StandardToken.constructor`)
```solidity
        uint256 totalSupply_,
```



Variable Names Too Similar

The contract has unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to different compiler versions. This can lead to an ambiguity when debugging as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.

FGD

Highlights & Alerts

This is just a placeholder

highlight placeholder lorem Ipsum...

highlight lorem

This is a alert demo

Alert demo

Code Audit History

6

0

5

0

1