PYE

Smart Contract Audit Report

Audit Summary

PYE is a new BEP-20 token on the Binance Smart Chain.

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

Audit Findings

Please ensure trust in the team prior to investing as their Staking contract owns a large portion of the total supply.
Date: March 14th, 2022.

Finding #1 - PYE - Informational

Description: The increaseAllowance and decreaseAllowancefunctions are declared public, but are never called internally.
Recommendation: These functions should be declared external for additional gas savings on each call.

---

Finding #2 - PYE - Informational

Description: Although the Ownable contract is inherited, the contract does not contain any ownership-restricted functions.
Recommendation: The Ownable contract could be safely removed to reduce contract size and deployment costs.

Contract Overview

• The total supply of the token is set to 10 billion $PYE [10,000,000,000].
• No mint or burn functions are present though the circulating supply can be decreased by sending tokens to the 0x..dead address.
• At the time of writing this report, there are 3,626 total token holders. The token allocation is as follows:
  • 80.79% of the total supply belongs to the CherryChefV2 contract. This contract was out of scope for the purpose of this audit.
  • 30% of the total supply has been sent to the 0x..dead address.
  • 1.7% of the total supply belongs to the deployer.
  
  
• There are no fees associated with transferring tokens.
• No ownership-restricted functions are present.
• The contract utilizes the SafeMath library to protect from overflows/underflows.
• The contract complies with the BEP-20 token standard.

Audit Results

Inheritance Chart

Function Graph

Functions Overview

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

 + [Int] IBEP20 
    - [Ext] totalSupply
    - [Ext] decimals
    - [Ext] symbol
    - [Ext] name
    - [Ext] getOwner
    - [Ext] balanceOf
    - [Ext] transfer #
    - [Ext] allowance
    - [Ext] approve #
    - [Ext] transferFrom #

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

 + [Lib] SafeMath 
    - [Int] add
    - [Int] sub
    - [Int] sub
    - [Int] mul
    - [Int] div
    - [Int] div
    - [Int] mod
    - [Int] mod

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

 +  PYEToken (Context, IBEP20, Ownable)
    - [Pub]  #
    - [Ext] getOwner
    - [Ext] decimals
    - [Ext] symbol
    - [Ext] name
    - [Ext] totalSupply
    - [Ext] balanceOf
    - [Ext] transfer #
    - [Ext] allowance
    - [Ext] approve #
    - [Ext] transferFrom #
    - [Pub] increaseAllowance #
    - [Pub] decreaseAllowance #
    - [Int] _transfer #
    - [Int] _burn #
    - [Int] _approve #
    - [Int] _burnFrom #

About SourceHat

SourceHat (formerly Solidity Finance - founded in 2020) has quickly grown to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1700+ solidity smart contract audits covering all major project types and protocols, securing a total of over $50 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 SourceHat Audit?

Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A SourceHat 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.

• Go Home