Dulion Info

In response to the growing worldwide population and its resulting gradual impact on the world economy, blockchain technology became available to transform the digital economy of the globe by way of the development of crypto money through a group of peers. Therefore, we made the decision to introduce a deflationary token with an anti-whale mechanism integrated as well as other criteria to combat rug pull, dumps, and whales with the intention of rewarding its investors.

Dulion 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.

88.99
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

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x5038...6937
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/07/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.

Contract cannot be locked

Owner cannot lock any user funds.

Token cannot be burned

There is no burning within the contract without any allowances

Ownership is renounced

Contract cannot 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.


No Audit Comments.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
Token.sol
L842
L1072
Description

Rename the local variables that shadow another component. Rename the local variables that shadow another component. In this case, ”owner” is shadowing the variable with the Ownable contract’s “owner” variable

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
Token.sol
L901
L910
L924
L928
L932
L949
L953
L960
L972
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Token.sol
L779
Description

Check that the address is not zero.

informational Issues | 4 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
Token.sol
L359-380
L319-321
L329-331
L344-346
L354-357
L266-275
L293-299
L238-241
L437-447
L410-419
L426-429
L421-424
L395-397
L399-401
L211-213
L227-230
Description

Remove unused functions.

Pending

#2 informational Issue
Function initializing state variables (function-init-state)
Token.sol
L737
L740
L743
L746
L749
Description

Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.

Pending

#3 informational Issue
Unused return values (unused-return)
Token.sol
L1233-1246
Description

Ensure that all the return values of the function calls are used.

Pending

#4 informational Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
Token.sol
L6-695
Description

We recommend importing all packages from npm directly without flatten the contract. Functions could be modified or can be susceptible to vulnerabilities