TapDaDoge Info

TapDaDoge promises an easily accessible, endlessly entertaining and rewarding experience. The player (You) takes control of their NFT Characters to jump over obstacles and in the process, earns various types of Points, which can be used in exchange for more goodies. The game is meant to have simple and intuitive mechanics that are tough to master but highly rewarding. Now, let’s get acquainted with our main cast of Characters (NFTs). Below are a limited sample of our Furry Friends, also known as “Doges”. You’ll notice that they have each been assigned a designation (e.g. “Unique”, “Legendary”, et cetera.).

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

0.02
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

Select the audit
"Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review"
Contract address
N/A
Network N/A
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2025/03/28
Revision date 2025/03/28

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 can mint

It is possible to mint new tokens.

Contract owner cannot blacklist addresses.

It is not possible to lock user funds by blacklisting addresses.

Contract owner can set high fees

Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.

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 not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

Contract is not upgradeable

The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.

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
Token.sol
  • The owner can set addresses as minters or revoke their minting privileges
  • The owner can mark addresses as trading pairs or remove them
  • The owner can set the time when fees should stop being collected.
  • The owner can update buy and sell fee percentages (up to 20%).
  • The owner can exclude addresses from fees.
  • The owner can withdraw all collected fees to their address.

Note - This Audit report consists of a security analysis of the TapDaDoge smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the mentioned contract for the TapDaDoge 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

medium Issues | 1 findings

Pending

#1 medium Issue
Missing Fee Validation in Constructor
Token.sol
L36-46
Description

The contract contains the functionality where the constructor accepts _buyFee and _sellFee parameters without any validation, allowing potential deployment with excessively high fees. While the setBuySellFee function properly limits fees to a maximum of 20%, this restriction is absent during contract initialization, creating a security inconsistency.

low Issues | 2 findings

Pending

#1 low Issue
Missing zero or dead address check.
Token.sol
L48-50
L52-54
L93-95
Description

It is recommended to check that the address cannot be zero or dead address.

Pending

#2 low Issue
Missing events arithmetic
Token.sol
L48-50
L52-54
L56-58
Description

It is recommended to emit all the critical parameter changes.

informational Issues | 1 findings

Pending

#1 informational Issue
Floating pragma solidity version
Token.sol
L2
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.