Dogecollie
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.
Owner privileges
Comments
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
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, 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.
Functions
public
36
State variables
public
12
Total lines
of code
477
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
medium Issues
Pending
#1 Issue
Funder can take out whole contract tokens
L459
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
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L276
L309
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Zero Address Validation (missing-zero-check)
L450
Check that the address is not zero.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L317-326
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L125-127
L134-137
L139-143
L259-261
L267-274
L276-283
L285-292
L294-306
Use the `external` attribute for functions never called from the contract.
Diagrams
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.