DogeTwit
DogeTwit is the first project of the Dogecoin ecosystem built on the BSC (Binance Smart Chain). DogeTwit is a combination of Dogecoin and Twitter: Dogeverse, building a social network that allows users to share memes and GIFs on the metaverse. To help users easily create and share content, DogeTwit integrates meme creation and NFT marketplace. Platform users can earn rewards such as native tokens or receive NFT items.
Owner privileges
Comments
- Excluded addresses cannot call the deliver function
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
3
Total lines
of code
493
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
Owner can regain ownership
L148-160
The owner is able to call the "lock" function to set the "_previousOwner". Now the owner is able to call the "unlock" function to get the ownership back also if the ownership was transferred to another address. We recommend you to set the "_previousOwner" in the "unlock" function also to address zero while transferring the ownership.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L225
L396
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L314-317
L319-322
Emit an event for critical parameter changes.
informational Issues
Pending
#1 Issue
Remove SafeMath library
-
We recommend you to remove the SafeMath library since the pragma version is above 0.8.x. It is implemented by default.
Pending
#2 Issue
Cannot take out the address balance
-
Since the contract can receive native tokens, the owner is not able to get out the balance of the contract. We recommend you to implement a function that the owner is able to take out the native token balance of the contract. Otherwise the native tokens are lost.
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.