FtheCo2

Smart Contract Audit Report

Audit Summary

FtheCo2 Audit Report FtheCo2 is a new BEP-20 token on the Binance Smart Chain that is an automatic liquidity providing protocol.

For this audit, we reviewed the project team's BasicToken contract at 0xf2A170546890FC411FDE171bb6be46a5A73F66C2 on the Binance Smart Chain Mainnet.

Audit Findings

No findings were identified, though some centralized aspects are present.
Date: June 13th, 2022.

Contract Overview

  • The initial supply of the token is set to 1 billion $FCO [1,000,000,000].
  • Although a mint function is present in the contract, it can not be utilized as minting was permanently set to disabled upon deployment.
  • Any user can burn their own tokens to reduce the total supply.
  • Any user can burn tokens on another user's behalf if an allowance has been granted.
  • At the time of writing this report, there are 16 total token holders. The token allocation is as follows:
  • The contract enforces a maximum buy amount and maximum sell amount (determined by the owner) which imposes a limit to the number of tokens that can be transferred via Pancakeswap in a single transaction.
  • There is a Team fee, Liquidity fee, and Burn fee on all transfers via Pancakeswap where neither the sender nor the recipient is excluded from fees.
  • The owner can set up to 9 Team fee recipients that are each assigned a unique buy fee and sell fee percentage. Each Team fee is applied on all buy and sell transactions per recipient.
  • Upon adding Team fee recipients, the owner will also specify whether the tokens collected from the fee will be sent to the recipient directly or will be swapped for BNB and subsequently sent to the recipient.
  • The tokens collected through the Burn fee are removed from the total supply.
  • The Liquidity fee charged during transfers is stored in the contract address. The tokens are swapped for BNB for the purpose of funding Pancakeswap liquidity and Team fee wallets when the caller is not initiating a buy transaction via Pancakeswap and the number of tokens collected through the Liquidity fee is greater than 0.
  • Liquidity-adds are automatically performed by selling the tokens collected as fees, pairing the received BNB with the token, and adding it as liquidity to the BNB pair.
  • The LP tokens received through this process are sent to the owner. We recommend that the team lock these newly acquired LP tokens.
  • The contract utilizes the SafeMath library to protect against overflows/underflows.
  • The contract complies with the BEP-20 token standard.
Ownership Controls:
  • The owner can set the Liquidity fee and Burn fee to any percentages at any time.
  • The owner can add up to 9 accounts as a Team fee recipient and set the buy fee and sell fee associated with the address to any value at any time.
  • The owner can pause/unpause trading at any time.
  • The owner can set the maximum buy amount and maximum sell amount to any values at any time.
  • The owner can exclude and include accounts from transfer fees at any time.

Audit Results

Vulnerability CategoryNotesResult
Arbitrary Jump/Storage WriteN/APASS
Centralization of Control
  • The owner can set each fee up to 100%.
  • The LP tokens generated through automatic liquidity adds are sent to the owner.
  • The team currently owns a large portion of the total supply.
WARNING
Compiler IssuesN/APASS
Delegate Call to Untrusted ContractN/APASS
Dependence on Predictable VariablesN/APASS
Ether/Token TheftN/APASS
Flash LoansN/APASS
Front RunningN/APASS
Improper EventsN/APASS
Improper Authorization SchemeN/APASS
Integer Over/UnderflowN/APASS
Logical IssuesN/APASS
Oracle IssuesN/APASS
Outdated Compiler VersionN/APASS
Race ConditionsN/APASS
ReentrancyN/APASS
Signature IssuesN/APASS
Unbounded LoopsN/APASS
Unused CodeN/APASS
Overall Contract Safety PASS

Inheritance Chart

Smart Contract Audit - Inheritance

Function Graph

Smart Contract Audit - Graph

Functions Overview


 ($) = payable function
 # = non-constant function
 
 Int = Internal
 Ext = External
 Pub = Public

 + [Int] IERC20 
    - [Ext] totalSupply
    - [Ext] balanceOf
    - [Ext] transfer #
    - [Ext] allowance
    - [Ext] approve #
    - [Ext] transferFrom #

 + [Int] IERC20Metadata (IERC20)
    - [Ext] name
    - [Ext] symbol
    - [Ext] decimals

 +  Context 
    - [Int] _msgSender
    - [Int] _msgData

 +  ERC20 (Context, IERC20, IERC20Metadata)
    - [Pub]  #
    - [Pub] name
    - [Pub] symbol
    - [Pub] decimals
    - [Pub] totalSupply
    - [Pub] balanceOf
    - [Pub] transfer #
    - [Pub] allowance
    - [Pub] approve #
    - [Pub] transferFrom #
    - [Pub] increaseAllowance #
    - [Pub] decreaseAllowance #
    - [Int] _transfer #
    - [Int] _mint #
    - [Int] _burn #
    - [Int] _approve #
    - [Int] _spendAllowance #
    - [Int] _beforeTokenTransfer #
    - [Int] _afterTokenTransfer #

 +  ERC20Burnable (Context, ERC20)
    - [Pub] burn #
    - [Pub] burnFrom #

 +  Pausable (Context)
    - [Pub]  #
    - [Pub] paused
    - [Int] _pause #
       - modifiers: whenNotPaused
    - [Int] _unpause #
       - modifiers: whenPaused

 +  Ownable (Context)
    - [Pub]  #
    - [Pub] owner
    - [Pub] renounceOwnership #
       - modifiers: onlyOwner
    - [Pub] transferOwnership #
       - modifiers: onlyOwner
    - [Int] _transferOwnership #

 +  ReentrancyGuard 
    - [Pub]  #

 +  BasicToken (ERC20, ERC20Burnable, Pausable, Ownable, ReentrancyGuard)
    - [Pub]  #
       - modifiers: ERC20
    - [Pub] decimals
    - [Ext]  ($)
    - [Int] _transfer #
       - modifiers: whenNotPaused
    - [Ext] mint #
       - modifiers: onlyOwner
    - [Ext] pause #
       - modifiers: onlyOwner
    - [Ext] unpause #
       - modifiers: onlyOwner
    - [Ext] addFeeRecipient #
       - modifiers: onlyOwner
    - [Ext] removeFeeRecipient #
       - modifiers: onlyOwner
    - [Ext] addNonFeePayer #
       - modifiers: onlyOwner
    - [Ext] removeNonFeePayer #
       - modifiers: onlyOwner
    - [Ext] setBurnFee #
       - modifiers: onlyOwner
    - [Ext] setLiquidityFee #
       - modifiers: onlyOwner
    - [Ext] setBuyLiquidityFee #
       - modifiers: onlyOwner
    - [Ext] setSellLiquidityFee #
       - modifiers: onlyOwner
    - [Ext] setMaxBuyAmount #
       - modifiers: onlyOwner
    - [Ext] setMaxSellAmount #
       - modifiers: onlyOwner
    - [Ext] includeOwnerFromFees #
       - modifiers: onlyOwner
    - [Ext] excludeOwnerFromFees #
       - modifiers: onlyOwner
    - [Prv] payFeesInBnb #
       - modifiers: doNotApplyFees
    - [Prv] swapToBNB #
    - [Prv] getLiquidityFee
    - [Int] isBuy
    - [Int] isSell

 + [Int] IPancakeRouter 
    - [Ext] WETH
    - [Ext] factory
    - [Ext] swapExactTokensForETHSupportingFeeOnTransferTokens #
    - [Ext] swapExactTokensForETH #
    - [Ext] addLiquidityETH ($)
    - [Ext] getAmountsOut

 + [Int] IPancakeFactory 
    - [Ext] createPair #

 + [Int] IPancakePair 

About Solidity Finance

Solidity Finance was founded in 2020 and quickly grew to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1300+ solidity smart contract audits covering all major project types and protocols, securing a total of over $10 billion U.S. dollars in on-chain value.
Our firm is well-reputed in the community and is trusted as a top smart contract auditing company for the review of solidity code, no matter how complex. Our team of experienced solidity smart contract auditors performs audits for tokens, NFTs, crowdsales, marketplaces, gambling games, financial protocols, and more!

Contact us today to get a free quote for a smart contract audit of your project!

What is a Solidity Audit?

Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A Solidity Audit takes this a step further by verifying economic logic to ensure the stability of smart contracts and highlighting privileged functionality to create a report that is easy to understand for developers and community members alike.

How Do I Interpret the Findings?

Each of our Findings will be labeled with a Severity level. We always recommend the team resolve High, Medium, and Low severity findings prior to deploying the code to the mainnet. Here is a breakdown on what each Severity level means for the project:

  • High severity indicates that the issue puts a large number of users' funds at risk and has a high probability of exploitation, or the smart contract contains serious logical issues which can prevent the code from operating as intended.
  • Medium severity issues are those which place at least some users' funds at risk and has a medium to high probability of exploitation.
  • Low severity issues have a relatively minor risk association; these issues have a low probability of occurring or may have a minimal impact.
  • Informational issues pose no immediate risk, but inform the project team of opportunities for gas optimizations and following smart contract security best practices.