What Do You Meme
Welcome to What Do You Meme! My name is Menno. If you want to contact me for some reason, reach out to [email protected]. But let's talk in third person so it looks more professional (or weird), right Richard Heart? $WDYM was created by Menno, a youtuber from the Netherlands, checking out crypto, while the camera is on, while uploading it on Youtube.. Don't sue him. The goal is simple. We want to build the smartest, happiest and therefore the richest community in crypto. And what has a stronger community than a hyped crypto memecoin? Then again, most memecoins have no utility. We combine those 2 by building hype while bringing a real utility that puts the community first & which makes the $WDYM token VERY deflationary without any sketchy ponzinomics!
Owner privileges
Comments
Ownership Privileges
The ownership has been renounced and the privileges mentioned below are not Valid Anymore
- Trigger tax functionality manually
- Include/Exclude accounts from fees
- Enable/Disable tax
- Set tax wallets
Note - This Audit report consists of a security analysis of the What Do You Meme 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 What Do You Meme team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.
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
94
State variables
public
2
Total lines
of code
1098
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
Resolved
#1 Issue
Fees can be 100% or more
L1047
L1057
The owner is able to set the Buy and Sell Tax up to 100% or even more, which is not recommended as it may cause the users to lose their funds.
low Issues
Pending
#1 Issue
Missing Events
L1014
Emit Events for critical parameter changes
Pending
#2 Issue
Unused state variables (unused-state)
L835
L836
L837
L838
L840
L841
L842
L843
L845
L846
L847
L848
Remove unused state variables.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L121-123
L605-608
L617-620
Remove unused functions.
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.