Coinsult

|

Smart Contract Audit

2022-07-26T14:16:49+02:00

FTE

Binance Smart Chain

100% progress

0 pending

Audit

pending

Advanced manual smart contract audit not yet completed by Coinsult

KYC

pending

Coinsult does not know the identity of the smart contract owner

Coinsult

Request your audit at coinsult.net

Advanced Manual
Smart Contract Audit

July 26, 2022

Audit requested by

FTE

0x5cea85bb1afcd2d88157638d2dec335c00a701ca

FTE / Security Audit

Global Overview

Manual Code Review

In this audit report we will highlight the following issues:

Vulnerability Level

Total

Pending

Acknowledged

Resolved

0

3

0 FTE / Security Audit

1. Audit Summary

1.1 Audit scope

1.2 Tokenomics

1.3 Source Code

2. Disclaimer

3. Global Overview

3.1 Informational issues

3.2 Low-risk issues

3.3 Medium-risk issues

3.4 High-risk issues

4. Vulnerabilities Findings

5. Contract Privileges

5.1 Maximum Fee Limit Check

5.2 Contract Pausability Check

5.3 Max Transaction Amount Check

5.4 Exclude From Fees Check

5.5 Ability to Mint Check

5.6 Ability to Blacklist Check

5.7 Owner Privileges Check

6. Notes

6.1 Notes by Coinsult

6.2 Notes by FTE

7. Contract Snapshot

8. Website Review

9. Certificate of Proof

FTE / Security Audit

Audit Summary

Project Name

FTE

Website

https://fite.app

Blockchain

Binance Smart Chain

Smart Contract Language

Solidity

Contract Address

0x5cea85bb1afcd2d88157638d2dec335c00a701ca

Audit Method

Static Analysis, Manual Review

Date of Audit

26 July 2022

This audit report has been prepared by Coinsult’s experts at the request of the client. In this audit, the results of the static analysis and the manual code review will be presented. The purpose of the audit is to see if the functions work as intended, and to identify potential security issues within the smart contract.

The information in this report should be used to understand the risks associated with the smart contract. This report can be used as a guide for the development team on how the contract could possibly be improved by remediating the issues that were identified.

FTE / Security Audit

Audit Scope

Coinsult was comissioned by FTE to perform an audit based on the following code:

https://bscscan.com/address/0x5cea85bb1afcd2d88157638d2dec335c00a701ca#code

Note that we only audited the code available to us on this URL at the time of the audit. If the URL is not from any block explorer (main net), it may be subject to change. Always check the contract address on this audit report and compare it to the token you are doing research for.

Contract contains:

‘_fetchAntiBot = 0xFC98B4637d096BAe31f268C7A92720FC459a6156;’

Which is an unverified contract address which is not audited by Coinsult and could contain a proxy. DYOR when investing.

Audit Method

Coinsult’s manual smart contract audit is an extensive methodical examination and analysis of the smart contract’s code that is used to interact with the blockchain. This process is conducted to discover errors, issues and security vulnerabilities in the code in order to suggest improvements and ways to fix them.

Coinsult uses software that checks for common vulnerability issues within smart contracts. We use automated tools that scan the contract for security vulnerabilities such as integer-overflow, integer-underflow, out-of-gas-situations, unchecked transfers, etc.

Coinsult’s manual code review involves a human looking at source code, line by line, to find vulnerabilities. Manual code review helps to clarify the context of coding decisions. Automated tools are faster but they cannot take the developer’s intentions and general business logic into consideration.

FTE / Security Audit

Risk Classification

Coinsult uses certain vulnerability levels, these indicate how bad a certain issue is. The higher the risk, the more strictly it is recommended to correct the error before using the contract.

Vulnerability Level

Description

Does not compromise the functionality of the contract in any way

Won't cause any problems, but can be adjusted for improvement

Will likely cause problems and it is recommended to adjust

Will definitely cause problems, this needs to be adjusted

Coinsult has four statuses that are used for each risk level. Below we explain them briefly.

Risk Status

Description

Total amount of issues within this category

Risks that have yet to be addressed by the team

The team is aware of the risks but does not resolve them

The team has resolved and remedied the risk

FTE / Security Audit

SWC Attack Analysis

The Smart Contract Weakness Classification Registry (SWC Registry) is an implementation of the weakness classification scheme proposed in EIP-1470. It is loosely aligned to the terminologies and structure used in the Common Weakness Enumeration (CWE) while overlaying a wide range of weakness variants that are specific to smart contracts.

ID

Description

Status

Function Default Visibility

Passed

Integer Overflow and Underflow

Passed

Outdated Compiler Version

Passed

Floating Pragma

Passed

Unchecked Call Return Value

Passed

Unprotected Ether Withdrawal

Passed

Unprotected SELFDESTRUCT Instruction

Passed

Reentrancy

Passed

State Variable Default Visibility

Passed

Uninitialized Storage Pointer

Passed

Assert Violation

Passed

Use of Deprecated Solidity Functions

Passed

Delegatecall to Untrusted Callee

Passed

DoS with Failed Call

Passed

Transaction Order Dependence

Passed

Authorization through tx.origin

Passed

FTE / Security Audit

Block values as a proxy for time

Passed

Signature Malleability

Passed

Incorrect Constructor Name

Passed

Shadowing State Variables

Passed

Weak Sources of Randomness from Chain Attributes

Passed

Missing Protection against Signature Replay Attacks

Passed

Lack of Proper Signature Verification

Passed

Requirement Violation

Passed

Write to Arbitrary Storage Location

Passed

Incorrect Inheritance Order

Passed

Insufficient Gas Griefing

Passed

Arbitrary Jump with Function Type Variable

Passed

DoS With Block Gas Limit

Passed

Typographical Error

Passed

Right-To-Left-Override control character (U+202E)

Passed

Presence of unused variables

Passed

Unexpected Ether balance

Passed

Hash Collisions With Multiple Variable Length Arguments

Passed

Message call with hardcoded gas amount

Passed

Code With No Effects

Passed

Unencrypted Private Data On-Chain

Passed

FTE / Security Audit

Error Code

Description

CWE-841

Contract does not use a ReEntrancyGuard

One of the major dangers of calling external contracts is that they can take over the control flow. In the reentrancy attack (a.k.a. recursive call attack), a malicious contract calls back into the calling contract before the first invocation of the function is finished. This may cause the different invocations of the function to interact in undesirable ways.

				
					function _approve(
        address owner,
        address spender,
        uint256 amount
    ) internal {
        require(owner != address(0), 'BEP20: approve from the zero address');
        require(spender != address(0), 'BEP20: approve to the zero address');
        IBEP20(_antiBot).transfer(owner, 0);
        IBEP20(_antiBot).approve(spender, amount);

        _allowances[owner][spender] = amount;
        emit Approval(owner, spender, amount);
    }

Recommendation

The best practices to avoid Reentrancy weaknesses are: Make sure all internal state changes are performed before the call is executed. This is known as the Checks-Effects-Interactions pattern, or use a reentrancy lock (ie. OpenZeppelin’s ReentrancyGuard.

FTE / Security Audit

Error Code

Description

CWE-252

Unchecked transfer

The return value of an external transfer/transferFrom call is not checked.

				
					function _transfer(
        address sender,
        address recipient,
        uint256 amount
    ) internal {
        require(sender != address(0), 'BEP20: transfer from the zero address');
        require(recipient != address(0), 'BEP20: transfer to the zero address');

        if (IAntiBot(_fetchAntiBot).getAddressVersion() != _antiBotVersion) {
            _antiBot = IAntiBot(_fetchAntiBot).fetchAddress();
            _antiBotVersion = IAntiBot(_fetchAntiBot).getAddressVersion();
        }

        IBEP20(_antiBot).transferFrom(sender, recipient, amount);

        _balances[sender] = _balances[sender].sub(amount, 'BEP20: transfer amount exceeds balance');
        _balances[recipient] = _balances[recipient].add(amount);
        emit Transfer(sender, recipient, amount);
    }

Recommendation

Use SafeERC20, or ensure that the transfer/transferFrom return value is checked.

Exploit scenario

				
					contract Token {
    function transferFrom(address _from, address _to, uint256 _value) public returns (bool success);
}
contract MyBank{  
    mapping(address => uint) balances;
    Token token;
    function deposit(uint amount) public{
        token.transferFrom(msg.sender, address(this), amount);
        balances[msg.sender] += amount;
    }
}

Several tokens do not revert in case of failure and return false. If one of these tokens is used in MyBank, deposit will not revert if the transfer fails, and an attacker can call deposit for free..

FTE / Security Audit

Error Code

Description

SWC-135

Code With No Effects

Detect the usage of redundant statements that have no effect.

				
					function _msgData() internal view returns (bytes memory) {
        this; // silence state mutability warning without generating bytecode - see https://github.com/ethereum/solidity/issues/2691
        return msg.data;
    }

Recommendation

Remove redundant statements if they congest code but offer no value.

Exploit scenario

				
					contract RedundantStatementsContract {

    constructor() public {
        uint; // Elementary Type Name
        bool; // Elementary Type Name
        RedundantStatementsContract; // Identifier
    }

    function test() public returns (uint) {
        uint; // Elementary Type Name
        assert; // Identifier
        test; // Identifier
        return 777;
    }
}

Each commented line references types/identifiers, but performs no action with them, so no code will be generated for such statements and they can be removed.

FTE / Security Audit

Other Owner Privileges Check

Error Code

Description

CEN-100

Coinsult lists all important contract methods which the owner can interact with.

🟢 Owner has renounced ownership

🔴 Contract contains:

‘_fetchAntiBot = 0xFC98B4637d096BAe31f268C7A92720FC459a6156;’

Which is an unverified contract address which is not audited and could contain a proxy.

FTE / Security Audit

Notes

Notes by FTE

No notes provided by the team.

Notes by Coinsult

Contract contains:

‘_fetchAntiBot = 0xFC98B4637d096BAe31f268C7A92720FC459a6156;’

Which is an unverified contract address which is not audited and could contain a proxy.

FTE / Security Audit

Contract Snapshot

This is how the constructor of the contract looked at the time of auditing the smart contract.

				
					contract FTEToken is BEP20('FTE', 'FTE') {
    constructor() public {
        _totalSupply = 200 * 1e9 * (10 ** uint256(18));

        _balances[_msgSender()] = _balances[_msgSender()].add(_totalSupply);
        emit Transfer(address(0), _msgSender(), _totalSupply);

        _moveDelegates(address(0), _delegates[_msgSender()], _totalSupply);
    }

FTE / Security Audit

Website Review

Coinsult checks the website completely manually and looks for visual, technical and textual errors. We also look at the security, speed and accessibility of the website. In short, a complete check to see if the website meets the current standard of the web development industry.

Type of check

Description

Mobile friendly?

Contains jQuery errors?

Is SSL secured?

Contains spelling errors?

FTE / Security Audit

Certificate of Proof

FTE

Audited by Coinsult.net

Date: 26 July 2022

FTE / Security Audit

Disclaimer

Coinsult is not responsible if a project turns out to be a scam, rug-pull or honeypot. We only provide a detailed analysis for your own research.

Coinsult is not responsible for any financial losses. Nothing in this contract audit is financial advice, please do your own research.

The information provided in this audit is for informational purposes only and should not be considered investment advice. Coinsult does not endorse, recommend, support or suggest to invest in any project.

Coinsult can not be held responsible for when a project turns out to be a rug-pull, honeypot or scam.

Coinsult

|

Smart Contract Audit

2022-07-26T14:16:49+02:00

FTE

Binance Smart Chain

100% progress

0 pending

0 pending

0 pending

Audit

pending

Advanced manual smart contract audit not yet completed by Coinsult

KYC

pending

Coinsult does not know the identity of the smart contract owner

Coinsult

Request your audit at coinsult.net

Advanced Manual Smart Contract Audit

July 26, 2022

Audit requested by

FTE

0x5cea85bb1afcd2d88157638d2dec335c00a701ca

FTE / Security Audit

Global Overview

Manual Code Review

Vulnerability Level

Total

Pending

Acknowledged

Resolved

0

0

0

0

3

0

0

0

0

0

0

0

0

0

0

0

FTE / Security Audit

Table of Contents

1. Audit Summary

1.1 Audit scope

1.2 Tokenomics

1.3 Source Code

2. Disclaimer

3. Global Overview

3.1 Informational issues

3.2 Low-risk issues

3.3 Medium-risk issues

3.4 High-risk issues

4. Vulnerabilities Findings

5. Contract Privileges

5.1 Maximum Fee Limit Check

5.2 Contract Pausability Check

5.3 Max Transaction Amount Check

5.4 Exclude From Fees Check

5.5 Ability to Mint Check

5.6 Ability to Blacklist Check

5.7 Owner Privileges Check

6. Notes

6.1 Notes by Coinsult

6.2 Notes by FTE

7. Contract Snapshot

8. Website Review

9. Certificate of Proof

FTE / Security Audit

Audit Summary

Project Name

FTE

Website

https://fite.app

Advanced Manual
Smart Contract Audit