Pokemoney

Smart Contract Audit Report

Audit Summary

Pokemoney Audit Report Pokemoney is building two new ERC-20 tokens.

For this audit, we reviewed the project team's PMY and NKG contracts at commit eddaf72d3305f394bae970615768bf6099551eee on the team's GitHub repository.

Audit Findings

Please ensure trust in the team prior to investing as they have substantial control in the ecosystem.
Date: March 7th, 2022.
Finding #1 - Pokemoney - Informational
Description: Several functions are declared public, but are never called internally.
NKG.mint, NKG.addMinter, NKG.delMinter, NKG.getMinter, NKG.delMinters, NKG.setExcludeAccountFromFee, PMY.mint, PMY.addMinter, PMY.delMinter
Recommendation: These functions should be declared external for additional gas savings on each call.

Contracts Overview

The contracts utilize the SafeMath library to protect against overflows/underflows.
The contracts comply with the ERC-20 token standard.
PMY Contract:
The initial supply of the token will be set upon deployment and minted to the owner.
The maximum supply of the token is set to 21 million $PMY [21,000,000.]
The contract utilizes a Minter role that allows the assigned addresses to mint any number of tokens to any address up to the maximum supply.
No burn functions are present though the circulating supply can be decreased by sending tokens to the 0x..dead address.
There was no token allocation for our team to analyze as the contract has yet to be deployed to the mainnet.

In order for all trading to take place on the platform, the owner must manually set the time when trading opens. Only accounts that have been manually whitelisted by the owner can trade before this specified time has passed.
The owner can update the contract's open trading time to any value at any time. All trading will be paused until the set time passes. If set to 0, trading can never be re-enabled for non-whitelisted users.
The owner can add/remove accounts from the transfer whitelist at any time.
The owner can add/remove accounts from the Minter role at any time.
There are no fees associated with transferring tokens.
NKG Contract:
The initial supply of the token will be set upon deployment and minted to the owner.
The contract utilizes a Minter role that allows the assigned addresses to mint any number of tokens to any address at any time.
No burn functions are present though the circulating supply can be decreased by sending tokens to the 0x..dead address.
There was no token allocation for our team to analyze as the contract has yet to be deployed to the mainnet.

In order for all trading to take place on the platform, the owner must manually set the time when trading opens. Only accounts that have been manually whitelisted by the owner can trade before this specified time has passed.
The owner can update the contract's open trading time to any value at any time. All trading will be paused until the set time passes. If set to 0, trading can never be re-enabled for non-whitelisted users.
The owner can add/remove accounts from the transfer whitelist at any time.
The owner can add/remove accounts from the Minter role at any time.
There are no fees associated with transferring tokens.

Audit Results

Vulnerability Category	Notes	Result
Arbitrary Jump/Storage Write	N/A	PASS
Centralization of Control	The owner can mint $PMY tokens up to the maximum supply cap, and mint an unlimited amount of $NKG at any time. The owner can pause trading for any non-whitelisted user at any time.	WARNING
Compiler Issues	N/A	PASS
Delegate Call to Untrusted Contract	N/A	PASS
Dependence on Predictable Variables	N/A	PASS
Ether/Token Theft	N/A	PASS
Flash Loans	N/A	PASS
Front Running	N/A	PASS
Improper Events	N/A	PASS
Improper Authorization Scheme	N/A	PASS
Integer Over/Underflow	N/A	PASS
Logical Issues	N/A	PASS
Oracle Issues	N/A	PASS
Outdated Compiler Version	N/A	PASS
Race Conditions	N/A	PASS
Reentrancy	N/A	PASS
Signature Issues	N/A	PASS
Unbounded Loops	N/A	PASS
Unused Code	N/A	PASS
Overall Contract Safety		PASS

PMY Contract

Smart Contract Audit - Inheritance

Smart Contract Audit - Graph


 ($) = 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 #

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

 + [Lib] EnumerableSet 
    - [Prv] _add #
    - [Prv] _remove #
    - [Prv] _contains
    - [Prv] _length
    - [Prv] _at
    - [Prv] _values
    - [Int] add #
    - [Int] remove #
    - [Int] contains
    - [Int] length
    - [Int] at
    - [Int] values
    - [Int] add #
    - [Int] remove #
    - [Int] contains
    - [Int] length
    - [Int] at
    - [Int] values
    - [Int] add #
    - [Int] remove #
    - [Int] contains
    - [Int] length
    - [Int] at
    - [Int] values

 + [Lib] SafeMath 
    - [Int] tryAdd
    - [Int] trySub
    - [Int] tryMul
    - [Int] tryDiv
    - [Int] tryMod
    - [Int] add
    - [Int] sub
    - [Int] mul
    - [Int] div
    - [Int] mod
    - [Int] sub
    - [Int] div
    - [Int] mod

 +  PMY (ERC20, Ownable)
    - [Pub]  #
       - modifiers: ERC20
    - [Pub] mint #
       - modifiers: onlyMinter
    - [Pub] addMinter #
       - modifiers: onlyOwner
    - [Pub] delMinter #
       - modifiers: onlyOwner
    - [Int] _isMinter
    - [Ext] setOpenSwapTimestamp #
       - modifiers: onlyOwner
    - [Ext] setWhiteListAccountsForTransfer #
       - modifiers: onlyOwner
    - [Int] _transfer #

NKG Contract

Smart Contract Audit - Inheritance

Smart Contract Audit - Graph


 ($) = 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 #

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

 + [Lib] EnumerableSet 
    - [Prv] _add #
    - [Prv] _remove #
    - [Prv] _contains
    - [Prv] _length
    - [Prv] _at
    - [Prv] _values
    - [Int] add #
    - [Int] remove #
    - [Int] contains
    - [Int] length
    - [Int] at
    - [Int] values
    - [Int] add #
    - [Int] remove #
    - [Int] contains
    - [Int] length
    - [Int] at
    - [Int] values
    - [Int] add #
    - [Int] remove #
    - [Int] contains
    - [Int] length
    - [Int] at
    - [Int] values

 + [Lib] SafeMath 
    - [Int] tryAdd
    - [Int] trySub
    - [Int] tryMul
    - [Int] tryDiv
    - [Int] tryMod
    - [Int] add
    - [Int] sub
    - [Int] mul
    - [Int] div
    - [Int] mod
    - [Int] sub
    - [Int] div
    - [Int] mod

 +  NKG (ERC20, Ownable)
    - [Pub]  #
       - modifiers: ERC20
    - [Pub] mint #
       - modifiers: onlyMinter
    - [Pub] addMinter #
       - modifiers: onlyOwner
    - [Pub] delMinter #
       - modifiers: onlyOwner
    - [Pub] getMinterLength
    - [Pub] isMinter
    - [Pub] getMinter
       - modifiers: onlyOwner
    - [Pub] delMinters #
       - modifiers: onlyOwner
    - [Ext] setTransferOpenTimestamp #
       - modifiers: onlyOwner
    - [Pub] setExcludeAccountFromFee #
       - modifiers: onlyOwner
    - [Int] _transfer #

About SourceHat

SourceHat has quickly grown to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1800+ 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!

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

SourceHat