Doge 3.0 Info

doge3.fun

The Ultimate Meme Token Phenomenon! Get ready to witness the meteoric rise of Doge 3.0 as we redefine the meme token landscape. Building upon the Doge hype, Doge 3.0 takes it to the next level, unleashing a tidal wave of excitement and opportunity. With 1% Tax and a renounced contract, it’s time to embrace the revolution, unleash the memes, and claim your destiny with Doge 3.0!

Overall Score
83.04
Poor Excellent
Doge 3.0 Logo

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

Smart Contract Audit

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x8e2A...D947
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/08/04
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 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 exclude wallets from fees.
  • The owner can transfer ownership.
  • The ownership of the contract is transferred to cxWallet address = (0xA828314168403eFd76E65209938cEfF1a431b0F5)
  • The swapped token balance of the contract is adding to marketing wallet address(0xA828314168403eFd76E65209938cEfF1a431b0F5).

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

low Issues | 1 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
Doge3.sol
L904
L962
Description

Rename the local variables that shadow another component.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
Doge3.sol
L811
L810
L817
L786-787
L825
L819
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
Doge3.sol
L427-429
L435-441
L885-887
L894-900
L903-908
L911-917
L920-933
L936-946
L949-959
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
Doge3.sol
L353-368
L153-164
L172-178
L191-203
L211-231
L278-288
L296-309
L239-249
L257-270
L98-104
L122-133
L341-351
L317-333
L32-34
L1081-1096
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
Doge3.sol
L811
Description

Remove unused state variables.