Self Auditing Eeyore Token prior to deployment
Self Audited by Cheyne From Degen Haus and Sirens Treasure
Disclaimer
This document may contain confidential information about its systems and intellectual property of the customer as well as information about potential vulnerabilities and methods of their exploitation. The report containing confidential information can be used internally by the customer or it can be disclosed publicly after all vulnerabilities are fixed - upon the decision of the customer.
Token for Audit
Eeyore Token 0xC9fc1A7fA5545F21E454C78957A5fD4a1D83A999
Project Scope
The scope of the project is a smart contract.
We have scanned this smart contract for commonly known and more specific vulnerabilities, below are those considered (the full list includes but is not limited to):
• Reentrancy
• Timestamp Dependence
• Gas Limit and Loops
• DoS with (Unexpected) Throw
• DoS with Block Gas Limit
• Transaction-Ordering Dependence
• Byte array vulnerabilities
• Style guide violation
• Transfer forwards all gas
• ERC20 API violation
• Malicious libraries
• Compiler version not fixed
• Unchecked external call - Unchecked math
• Unsafe type inference • Implicit visibility level
Executive Summary According to the assessment, the customer’s solidity smart contract is now Well Secured.
Automated checks are with smartDec, Mythril, Slither and remix IDE. All issues were performed by our team, which included the analysis of code functionality, the manual audit found during automated analysis were manually reviewed and applicable vulnerabilities are presented in the audit overview section. The general overview is presented in the AS-IS section and all issues found are located in the audit overview section. We found the following
Total Issues 1
Critical 0
High 0
Medium 0
Low 1
Very Low 0
Code Quality
The libraries within this smart contract are part of a logical algorithm.
A library is a different type of smart contract that contains reusable code. Once deployed on the blockchain (only once), it is assigned to a specific address and its properties/methods can be reused many times by other contracts. Eeyore Token team has not provided scenario and unit test scripts, which would help to determine the integrity of the code in an automated way. Overall, the code is well commented.
Commenting can provide rich documentation for functions, return variables and more. Use of the Ethereum Natural Language Specification Format (NatSpec) for commenting is recommended.
Use of Dependencies
As per our observation, the libraries are used in this smart contract infrastructure. Those were based on well known industry standard open source projects and even core code blocks that are written well and systematically.
AS-IS Overview
EeyoreToken.sol File And Function Level Report Contract: EEYORE Inherit: Context, IBEP20,
Ownable Observation: Passed
Test Report: Passed
Solidity Static Analysis
EeyoreToken.sol
Severity Definitions
Risk Level Description
Audit Findings Low:
Critical: No Critical severity vulnerabilities were found.
High: No high severity vulnerabilities were found.
Medium: No medium severity vulnerabilities were found.
Low: No low severity vulnerabilities were found.
Very Low: No very low severity vulnerabilities were found.
Conclusion
We were given a contract file and have used all possible tests based on the given object. So it is now ready for mainnet deployment. We have used all the latest static tools and manual observations to cover maximum possible test cases to scan everything.
The security state of the reviewed contract is
“Well Secured”.
Cheyne
Developer
Note For Contract Users
There are several owner only functions. Those can be called by the owner's wallet only. So, if the owner's wallet is compromised, then it carries the risk of the contract becoming vulnerable. Owner has full control over the smart contract. Thus, technical auditing does not guarantee the project's ethical side. Please do your due diligence before investing. Our audit report is never an investment advice.
Last updated
