QR68
QR68 is a multichain DeFi protocol in the Arbitrum ecosystem. QR68 is a true Defi Crypto solution that is designed for easy and quick payments over QR codes. In order to facilitate private, peer-to-peer transactions, QR68 utilizes a private blockchain network that is effective and decentralized. To put it simply, QR68 enables fast and convenient transactions without the need for intermediaries or banks.
Owner privileges
Comments
Ownership Privileges:
- Set liquidity pool status to true or false
- Set marketing pool, Pool2, and treasury address
- Set taxes but not more than 9%
- Include/Exclude accounts from fee whitelist
- Set the minimum and max amount of swap tokens at, to any arbitrary value
- Withdraw the contract's balance to the marketingPool address
- Withdraw tokens, including native ones from the contract into the Pool2 address
We recommend investors/users do their own research before investing
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
222
Capabilities
Hover on items
Functions
public
8
State variables
public
0
Total lines
of code
250
Capabilities
Hover on items
Functions
public
3
State variables
public
0
Total lines
of code
56
Capabilities
Hover on items
Functions
public
0
State variables
public
0
Total lines
of code
27
Capabilities
Hover on items
Functions
public
4
State variables
public
0
Total lines
of code
77
Capabilities
Hover on items
Functions
public
6
State variables
public
0
Total lines
of code
75
Capabilities
Hover on items
Functions
public
59
State variables
public
0
Total lines
of code
200
Capabilities
Hover on items
Functions
public
0
State variables
public
0
Total lines
of code
132
Capabilities
Hover on items
Functions
public
0
State variables
public
0
Total lines
of code
52
Capabilities
Hover on items
Functions
public
15
State variables
public
16
Total lines
of code
230
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 specification 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)
L66
L225
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L125-127
L128-130
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L85
L90
L95
Check that the address is not zero.
Pending
#4 Issue
Floating Pragma
-
The current pragma Solidity directive is “^0.8.4". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L85-87
L95-101
L114-120
L128-139
L174-176
L184-193
L147-149
L157-166
L36-42
L60-65
L201-221
Remove unused functions.
Pending
#2 Issue
Functions that are not used (dead-code)
L203-209
L242-249
L184-190
Remove unused functions.
Pending
#3 Issue
Functions that are not used (dead-code)
L23-26
L19-21
Remove unused functions.
Pending
#4 Issue
Functions that are not used (dead-code)
L48-51
L42-46
L30-34
L22-28
L36-40
Remove unused functions.
Pending
#5 Issue
Unused state variables (unused-state)
L20
Remove unused state variables.
Pending
#6 Issue
Functions that are not used (dead-code)
L103-105
L120-131
L79-90
L44-46
L28-33
L103-105
L120-131
L79-90
L44-46
L59-68
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L29-31
L37-39
L53-55
Use the `external` attribute for functions never called from the contract.
Pending
#2 Issue
Public function that could be declared external (external-function)
L39-41
L46-48
L58-61
L66-68
L77-80
L94-106
L120-123
L139-146
Use the `external` attribute for functions never called from the contract.
Pending
#3 Issue
Public function that could be declared external (external-function)
L30-32
L56-59
L65-67
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.