Dogecollie Info
Dogecollie is a faithful guardian of God. They are agile and tenacious, as is our $Dogecollie community. $Dogecollie is a decentralized experiment launched on October 7, 2022 by founder Docoz, and is a new opportunity for those struggling with the biggest bear market since then. Born out of trials and tribulations, $Dogecollie community is the strongest community you can find, supporting each other and pushing each other to success. $Dogecollie does not have an assigned owner, but is owned by someone who wants to own it, DOCO is used in the Community Marketplace. By purchasing these goods and services through DOCO, users can enjoy better Discounts and offers, they can use DOCO tokens for more benefits and rewards. By developing a DDCE (DOCO decentralized community ecosystem) with #Doco as the core and store of value, we will co-create a stronger and more powerful community of faith that brings together believer (Christian) creators, investors, developers and holders, and guards this community as God does. Make the community more prosperous! And backed by $Doco.
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.
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.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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.
The Tech address is able to drain out the held tokens by the contract. Be aware of it
Owner privileges
- Update fund address
Notes:
- Funds will be send to the fund token distributor
- Addresses that were set as fund address will be a whitelisted fee address. After updating to a new fund address the previous one is still whitelisted. After updating to a new fund address remove the old one from the fee whitelist
- Anyone can call the claim balance function to send the whole contract balance to the tech address
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
Funder can take out whole contract tokens
The funder (tech address) is able to call the "claimToken" function and pass own contract address to drain out the contract. It is recommended to prevent passing own contract address to the function. Also it is confusing that the "onlyFunder" modifier is not called "onlyTech" instead. Because only the tech address is able to call the "claimToken" function and nobody is possible to change the tech address. Additionally add a function for the owner that he can update the tech address also.
low Issues | 2 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
optimization Issues | 1 findings
Pending
#1 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.