QR68 Info

qr68.com

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.

Overall Score
79.48
Poor Excellent
QR68 Logo

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

On-Chain Insights

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x8604...56f1
Network
Arbitrum - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/03/07
Revision date In progress

Summary and Final Words

No crucial issues found

The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.

Contract owner cannot mint

It is not possible to mint new tokens.

Contract owner cannot blacklist addresses.

It is not possible to lock user funds by blacklisting addresses.

Contract owner cannot set high fees

The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.

Contract cannot be locked

Owner cannot lock any user funds.

Token cannot be burned

There is no burn function within the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


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

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
BEP20_nopause.sol
L66
L225
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
BaseToken.sol
L125-127
L128-130
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
BaseToken.sol
L85
L90
L95
Description

Check that the address is not zero.

Pending

#4 low Issue
Floating Pragma
BaseToken.sol
-
Description

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

optimization Issues | 3 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
BEP20Detailed.sol
L29-31
L37-39
L53-55
Description

Use the `external` attribute for functions never called from the contract.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
BEP20_nopause.sol
L39-41
L46-48
L58-61
L66-68
L77-80
L94-106
L120-123
L139-146
Description

Use the `external` attribute for functions never called from the contract.

Pending

#3 optimization Issue
Public function that could be declared external (external-function)
BEPOwnable.sol
L30-32
L56-59
L65-67
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 6 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
Address.sol
L85-87
L95-101
L114-120
L128-139
L174-176
L184-193
L147-149
L157-166
L36-42
L60-65
L201-221
Description

Remove unused functions.

Pending

#2 informational Issue
Functions that are not used (dead-code)
BEP20_nopause.sol
L203-209
L242-249
L184-190
Description

Remove unused functions.

Pending

#3 informational Issue
Functions that are not used (dead-code)
BEPContext.sol
L23-26
L19-21
Description

Remove unused functions.

Pending

#4 informational Issue
Functions that are not used (dead-code)
SafeMathInt.sol
L48-51
L42-46
L30-34
L22-28
L36-40
Description

Remove unused functions.

Pending

#5 informational Issue
Unused state variables (unused-state)
SafeMathInt.sol
L20
Description

Remove unused state variables.

Pending

#6 informational Issue
Functions that are not used (dead-code)
SafeMath.sol
L103-105
L120-131
L79-90
L44-46
L28-33
L103-105
L120-131
L79-90
L44-46
L59-68
Description

Remove unused functions.