QDVI Info
QDVI is an innovative project aimed at building a luxury hotel complex in Kudowa-Zdrój, with a long-term vision for global development and expansion. Our mission is to deliver unparalleled hospitality experiences for the most discerning clients, offering not only comfortable spaces but also exceptional benefits and exclusive experiences that meet the expectations of modern travelers.
TrustNet Score
The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.
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.
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.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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
- The owner can update rewards per block.
- The owner can update the token price.
- The owner can update the minimum stake.
Note - This Audit report consists of a security analysis of the QDVI smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the QDVI team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 4 findings
Pending
#1 medium Issue
The owner can lock reward.
The contract contains the functionality in which the owner of the contract can lock the reward functionality in the contract for an indefinite period of time, which can lock the user funds in the contract. There must be a threshold limit so that the value will lie at that range to exclude this risk from the contract.
Pending
#2 medium Issue
Missing ‘NonReentrant’ check.
The contract imports the reentrancy guard in the contract but the staking or un-staking function does not have the reentrancy guard check. It is recommended to add the check-in function to avoid any reentrancy issues in the contract.
Pending
#3 medium Issue
Missing threshold for Max purchase.
The contract contains the functionality in which the admin of the contract can update any arbitrary value in the Token amount and Minimum stake, including zero, which can lock the swapping functionality in the contract if the value is set to zero. There must be a threshold limit so that the value will lie at that range to exclude this risk from the contract.
Pending
#4 medium Issue
Missing allowance check.
Within the stake() function, there is a potential issue because it does not verify whether the caller has granted sufficient ERC-20 token allowance before invoking transferFrom. Without an explicit allowance check, the function will simply attempt to execute the token transfer, potentially causing a revert if the allowance is insufficient. To enhance user experience and clarity, you can add a requirement statement, ensuring the user has granted the necessary approval. This change prevents unexpected reverts, provides more user-friendly feedback, and helps preserve gas costs by failing early.
low Issues | 2 findings
Pending
#1 low Issue
Missing events arithmetic.
It is recommended to emit all the critical parameter changes.
Pending
#2 low Issue
Floating pragma solidity version.
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
informational Issues | 1 findings
Pending
#1 informational Issue
Remove unused functions.
Functions that are not used (dead code).