DotNames Info

Welcome to dotNames! We're extremely excited to have you here with us, and equally excited that you've decided to integrate dotNames into your wallet/dApp. We built dotNames from the ground up with Solidity, and made the important functions easy to call and interact with.

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

54.06
Poor Excellent

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.

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x6C5A...d73D
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/03/02
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

The contract does not include owner functions that allow post-deployment modifications.

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.


Note: Ownership is renounced

Owner privileges

  • manually burn liquidity pair tokens with 0-10 percentage
    • Be aware of it because the owner can burn all LPs here after several calls
  • set auto lp burn settings
    • lp burn frquency must be above 10 minutes and the percentage is between 0-10%
  • Enable trading active (once only)
    • we recommend you to prevent the function call twice
  • Remove limits once
  • disable transfer delay once
  • update swap at tokens amount value
    • 0.001% to 0.5%
  • update TX amount
    • min 0.1%
  • update maxWallet amount
    • min 0.5%
  • Enable/disable swapping
  •  update buy fees
    • All buy fees must below 35%
  • update sell fees
    • All sell fees must below 40%
  • exclude from fees
  • set automated market maker pair
  • update following wallets
    • marketing
    • development

 

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
DotNames.sol
L660
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
DotNames.sol
L708-723
L725-731
L733-739
L752-762
L764-774
L1045-1061
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
DotNames.sol
L799
L807
Description

Check that the address is not zero.

Pending

#4 low Issue
Tautology or contradiction (tautology)
DotNames.sol
L1045-1061
Description

Fix the incorrect comparison by changing the value type or the comparison.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
DotNames.sol
L581
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
DotNames.sol
L41-43
L45-48
L112-114
L117-119
L122-124
L135-138
L141-143
L145-148
L150-164
L166-169
L171-179
L781-791
L812-814
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)
DotNames.sol
L17-19
L215-230
L300-302
L331-340
L316-318
L343-352
L320-329
L260-266
L285-290
L292-297
L276-283
L268-273
Description

Remove unused functions.