MetaDog, is bringing your favorite likable four-legged friends into the Metaverse! Own your MetaDog NFT, breed, train, and interact with other MetaDog owners in the coming Play 2 Earn game! Welcome to MetaDogg's life! MetaDog is a collection of 10,000 furry gamified digital dogs who've just broken out of the Meta pounds and are ready to find a precious NFT family to protect in the MetaDogg-verse! Story MetaDogs have been locked out of the Metaverse for far too long! And that's going to change on [DATE] when they're ready to meet their new master! Welcome to MetaDog, your friendly and zippy bunch of NFT puppies who want to make the Metaverse more lively. But make no mistake, behind that energetic doggy front, they're still looking to protect their MetaDogg-verse. With a front for the Metaverse, MetaDog brings new forms of utility to any NFT MetaDog owner, where they can control and rule the Meta pound as early MetaDogg adopters! As a proud MetaDog owner, proud NFT holders will have unrestricted access to our MetaDog-verse, where they can breed better versions of their MetaDogs and participate in entertaining games with their fuzzy four-legged metaverse counterparts! As a MetaDog owner, you will compete to become the one MetaDog everyone respects while we're crafting a way to reward your loyalty through token burning and play-2-earn features
- Update Pancake Router
- Include/Exclude wallets from all limits, FEES, and maximum holding limit.
- Set swap tokens at amount and marketing address.
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.
Hover on items
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.
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Contract doesn't import npm packages from source (like OpenZeppelin etc.)
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
Functions that are not used (dead-code)
Remove unused functions.
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
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.