Xeth Info
In the ever-evolving world of Decentralized Finance (DeFi), XETH VIP stands at the forefront, disrupting the landscape with its ground-breaking decentralized bot built on the Ethereum blockchain. A true game-changer, XETH VIP brings together specialized bots such as Sniping, Bridge, Farm, and GMX Perpetual, forming an unparalleled ecosystem for decentralized automation. Let's dive into the world of XETH VIP and explore how it empowers users to unlock the true potential of DeFi.
Team and KYC Verification
The team has securely submitted their personal information to SolidProof.io for verification.
In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.
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
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
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 whitelist addresses from fees.
- The owner can set the buy and sell fee between 1 to 10%.
- The owner can change the liquidity pair address.
- The owner can enable/disable the swap fees.
- The owner can change the marketing wallet address.
- The owner can change/add multiple presale addresses. Beware of it
- The owner can enable trading only once.
Note - The contract owner have addressed fees issue on the contract so marking it as acknowledged. This Audit report consists of a security analysis of the Xeth Token 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 Xeth team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.
Files and details
Findings and Audit result
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.
medium Issues | 1 findings
Resolved
#1 medium Issue
Fees will be 89% before the trading starts
The trading needs to be enabled by the owner in order for regular users to transfer tokens with regular fees. However, if a User tries to transfer tokens before the trading is enabled, the contract will automatically levy 89% fees.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 3 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Conformity to Solidity naming conventions (naming-convention)
Follow the Solidity [naming convention](https://solidity.readthedocs.io/en/v0.4.25/style-guide.html#naming-conventions).
Pending
#3 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.
A file with a different Hash has been intentionally or otherwise modified 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.