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.
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.
On-Chain Insights
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.
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.
Scope of Work
Files and details
This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.
- Review the specifications, sources, and instructions provided to SolidProof to ensure we understand the smart contract's size, scope, and functionality.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Specification comparison checks whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis determines whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution is analyzing a program to determine what inputs cause each part of a program to execute.
- Based on the established industry and academic practices, recommendations, and research, best practices review smart contracts to improve efficiency, effectiveness, clarity, maintainability, security, and control.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
Findings and Audit result
low Issues | 2 findings
Pending
#1 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#2 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
We recommend to import all packages from npm directly without flatten the contract. Functions could be modified or can be susceptible to vulnerabilities
medium Issues | 1 findings
Pending
#1 medium Issue
Owner needs to Enable Trading
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.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
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)
Remove unused functions.
Ownership Privileges
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.