SHEPE
Shiba Inu and Pepe Frog, two legendary meme characters, are stepping into the ring for an electrifying Street Fighter-style showdown in the world of cryptocurrencies! 🐕🐸 Prepare for an adrenaline-pumping adventure with Shiba vs Pepe, where meme warfare meets blockchain technology! Our innovative and decentralized meme-inspired token brings you the best of both worlds: the cuteness of Shiba Inu and the mischievousness of Pepe Frog, duking it out in the ultimate clash.
Owner privileges
Comments
Ownership Privileges
- The owner can remove the max transaction limit.
- The owner can finalize fees.
- The owner can enable/disable swapping.
- The owner can set the marketing wallet address.
- The owner can exclude/include wallets in fees.
- The owner can update the maximum and minimum threshold amounts of 1% and 0.3% of the total supply.
- The owner can enable trading only once.
- The owner can claim the stuck tokens.
- The buy fees and sell fees will be set to 40% before the trading is enabled.
The ownership has been renounced so the privileges are not applicable anymore
Note - This Audit report consists of a security analysis of the SHEPE 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 SHEPE team. Other contracts associated with the project were not audited by our team. We recommend investors 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
34
State variables
public
5
Total lines
of code
306
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 specification 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.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L167
L181
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing events arithmetic.
L251,252
Emit all the critical parameter changes.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L93
L94
L95
L96
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L35-37
L42-45
L51-54
L145-147
L148-150
L151-153
L154-156
L163-166
L167-169
L170-173
L174-180
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.