Hash2O
Hash20 is designed in such a way to open door of DeFi for everyone; making the decentralized financial world accessible for all; through a multi chain yield processing Hash: Hash20. The core idea behind the structure of this project, is to provide Hashers (The community of investors who invests through Hash20) the ease of investing in liquidity pools; without having to go through the hustle of wasting time and money in finding the right liquidity pool. Thus creating a safe and reliable atmosphere for novice investors; regardless of the hostilities in the DeFi space. Hash20 offers a judicious initiative, that operate through a set of algorithms that automatically diversify investments in reliable protocols. In a nutshell, the benefits gained through MetaHash are: Diversification of the portfolio, minimized risk, lower fee, life-time reward generation, NFT staking, lesser hustle and bustle, and lastly, eradication of unlimited time spent on research.
Owner privileges
Comments
- Owner is able to lock user funds by
- antibot functionality
- for more informations look in the "_beforeTokenTransfer" function in L50
- antibot functionality
- Owner is unable to set the pinkAntiBot address
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
Functions
public
0
State variables
public
0
Total lines
of code
216
Capabilities
Hover on items
Functions
public
0
State variables
public
0
Total lines
of code
23
Capabilities
Hover on items
Functions
public
11
State variables
public
0
Total lines
of code
355
Capabilities
Hover on items
Functions
public
4
State variables
public
2
Total lines
of code
59
Capabilities
Hover on items
Functions
public
6
State variables
public
0
Total lines
of code
81
Capabilities
Hover on items
Functions
public
3
State variables
public
0
Total lines
of code
27
Capabilities
Hover on items
Functions
public
3
State variables
public
0
Total lines
of code
71
Capabilities
Hover on items
Functions
public
0
State variables
public
0
Total lines
of code
98
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L27
L28
Rename the local variables that shadow another component.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L44-57
L68-79
L59-66
L28-35
Remove unused functions.
Pending
#2 Issue
Functions that are not used (dead-code)
L20-22
Remove unused functions.
Pending
#3 Issue
Functions that are not used (dead-code)
L274-289
L251-261
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L53-55
L61-64
Use the `external` attribute for functions never called from the contract.
Pending
#2 Issue
Public function that could be declared external (external-function)
L61-63
L69-71
L86-88
L93-95
L100-102
L112-115
L120-122
L131-134
L149-163
L177-180
L196-204
Use the `external` attribute for functions never called from the contract.
Diagrams
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.