TecVise Info
TecVise Games is a leading blockchain game development company. Our games offer unique gaming experiences, in-game asset ownership, and the ability to earn real-world value while playing. Through our platform, we develop and market not only our own games, but also those of other game developers. Our goal is to create a gaming platform for the best blockchain games. We plan to release these games and collaborations within the next few years, fundamentally changing the way gamers interact with virtual worlds.
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.
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
- Can enable and disable trading for an unlimited period.
- Set buy/sell taxes, but not more than 25% in this contract.
- Update Swap Threshold to any value. This means the swapping of the minimum fee amount collected in the contract. After swapping, the fee amount from the contract's balance will be credited to the marketing wallet
- Update the Router and Pair address of the DEX, which will facilitate the buying/selling of the tokens by this smart contract.
- Update the Marketing wallet address to which the fees will be credited after swapping the contract's balance.
- The owner can update the team wallet address to which the taxes will be credited after swapping the contract's balance.
- Include/Exclude Wallets from fees. The excluded wallets will not have to pay any kind of fee/tax.
- Withdraw all types of tokens from the contract's balance, including the native ones. If tokens are accidentally sent to the contract, then the owner will be able to rescue them and refund them to the correct individual after their internal verification.
Note - This Audit report consists of a security analysis of the TecVise smart contracts mentioned in these audit reports. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the contracts mentioned in these reports for the TecVise team. Our team did not audit other contracts associated with the project. 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 | 1 findings
Pending
#1 medium Issue
Owner can pause trading.
The owner can disable trading for an unlimited period of time for the users who are not whitelisted, as this can lock user funds, which is not recommended. Trading should not be disabled if it is enabled once.
low Issues | 3 findings
Pending
#1 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#3 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.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 1 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.