Snoopy Info

Snoopy Introduction Meet the legendary Snoopy! This beloved beagle has captured hearts worldwide with his charm and mischievous spirit. Now, get ready to embark on a thrilling adventure as Snoopy takes the spotlight in the exciting realm of Snoopy Token. Join us for a world of laughter, friendship, and endless possibilities. Get ready to experience the magic of Snoopy's universe like never before.

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

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

TrustNet DataPulse

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x4245...14E8
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/06/27
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 can blacklist addresses

It is 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
  • Include/Exclude wallets from the max transaction limit, maximum holding limit, and the bots list (blacklist functionality)
  • Set the maximum holding and transaction limit, and they must be greater than 0.1% of the total supply
  • Withdraw foreign tokens from the contract, but not the native ones
  • Enable Trading but cannot disable it.

Moreover, the funds can be locked by the owner because it is possible to manually add wallets or contracts to the list of bots. 

Note - This Audit report consists of a security analysis of the Snoopy 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 Snoopy team, other contracts associated with the project were not audited by our team. We recommend investors to do their 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
Owner needs to Enable Trading
L364
Description

The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can exclude addresses from the max txn manually and those addresses will be able to trade tokens. This functionality can be exploited in the following way, For example, there is a presale and the wallets used for the presale can be excluded from max txn by the owner. All the tokens obtained can be consolidated into a final wallet address and facilitate trading and selling of the acquired tokens, the last wallet address can be excluded from the max txn.

low Issues | 2 findings

Pending

#1 low Issue
Missing Events Arithmetic (events-maths)
Snoopy.sol
L409-415
L417-423
Description

Emit an event for critical parameter changes.

Pending

#2 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
Snoopy.sol
-
Description

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

optimization Issues | 2 findings

Pending

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

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
Snoopy.sol
L85-87
L89-91
L107-113
L115-120
L122-128
L130-145
L147-157
L159-171
L235-237
L239-245
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)
Snoopy.sol
L9-12
Description

Remove unused functions.