WAXCHAIN Info

WAXCHAIN is not just about a token but about building a comprehensive ecosystem that supports secure, efficient, profitable, and entertaining digital communications.

WAXCHAIN Logo

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.

67.09
PoorExcellent

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.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Select the audit
Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x8a11...1bb5
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/03/20
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.

Token transfer can be locked

Owner can lock user funds with owner functions.

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
  • The owner can start and end the presale in the contract.
  • The owner can set any arbitrary value as the price of the token.
  • The owner can set any arbitrary value as the price of a dollar in bnb.
  • The owner can pause the presale.
  • The owner can enable/disable claim functionality in the contract.
  • The owner can transfer contract balance to his wallet.
  • The owner can claim the stuck tokens including contract's tokens.

Note - This Audit report consists of a security analysis of the WAXCHAIN 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 WAXCHAIN 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

high Issues | 1 findings

Pending

#1 high Issue
The owner can manipulate the price of token.
WAXCHAIN.sol
L442-444
L447-449
Description

The owner can set any arbitrary value as the price of token in bnb and dollar which is not recommended as this can manipulate the price of tokens. Instead of making it manually, add the functionality to have the price of tokens and according to that the price will be pegged with USDT or BNB in the contract.

medium Issues | 1 findings

Pending

#1 medium Issue
The owner can lock token.
WAXCHAIN.sol
L454-456
Description

The owner can enable/disable the claim functionality from the contract which is not recommended as this can lock the user funds for an unlimited period of time. It is recommended that the claimed functionality should not be locked in the contract.

low Issues | 1 findings

Pending

#1 low Issue
Floating pragma solidity version
WAXCHAIN.sol
L12
Description

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)
WAXCHAIN.sol
L100-102
L104-107
L141-143
L149-151
L159-161
L164-166
L169-173
L180-184
L186-191
L194-198
L200-209
L331-389
L390-424
L433-435
L437-439
L442-444
L447-449
L451-453
L458-460
L462-464
Description

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)
WAXCHAIN.sol
L58-60
L247-263
Description

Remove unused functions.