Project overview - Shib Protocol

Type ERC20/BEP20
Language Solidity
Request date 2022/09/20
Latest Revision date 2022/09/20

SHIB PROTOCOL is here to present a new way to introduce your project token by providing a use case for your project token using the platform we developed (Auction Pool, Staking Pool, NFT Marketplace, B2E, Swap, Casino). We aim to be a platform that will give a use case for the newest project.

Price Chart

Audit Summary

Static analysis Dynamic analysis Symbolic Execution SWC check
Network Binance Smart Chain
License & Compiler Unlicense / v0.8.15+commit.e14f2714
Contract address 0xef6f1216f20369E48E08279dE034e3Cfac8a4D9b
Critical issues found The contract does contain issues of high or medium criticality. In some circumstances, the Contract may not function as intended and may pose a safety risk.
Contract owner cannot mint It's not possible to mint new tokens.
Contract owner cannot blacklist addresses. It's not possible to lock user funds by blacklisting addresses.
Contract owner cannot set fees above 25% The fees can be a maximum of 25%. The contract can therefore not be locked.
Contract cannot be locked Owner can't lock any user funds.
Token cannot be burned There is no burn function within the contract.
Ownership is not renounced Contract can be manipulated by owner functions.
No Issues found.
No Issues found.
1 Issue found. 0 resolved.
4 Issues found. 0 resolved.
3 Issues found. 0 resolved.
No Issues found.

The owner can:

  • Claim stuck tokens but not the native ones. Moreover, the owner can pass the zero address to the function and withdraw the contract's balance.
  • Update the uniswap router address and update the AMM Pair
  • Exclude/Include wallets from fees
  • Update the marketing and liquidity fee shares but it cannot be more than 100
  • Change marketing wallet address.
  • Set the amount to swap tokens at.
  • Include/Exclude accounts from maximum wallet limits and set maximum wallet amount but it cannot go below 1%
  • Set the maximum transaction limit that cannot be lower than 0.1% of the supply

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)
The auditing process follows a routine series of steps:
  • 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.

Public functions Public state variables Total lines of code Capabilities
105 16 843

Public functions Public state variables Total lines of code Capabilities
105 16 843

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.

#2 | Access Control
Severity Location Status
Medium Shib_Protocol.sol : 524 Pending

This function should not be public as anyone can call the launch function and that may be catastrophic for the project

#1 | Missing Events Arithmetic (events-maths)
Severity Location Status
Low Shib_Protocol.sol : 524,530, 600, 759-762 Pending

Emit an event for critical parameter changes.

#2 | Missing Zero Address Validation (missing-zero-check)
Severity Location Status
Low Shib_Protocol.sol : 469, 487-488, 556-557 Pending

Check that the address is not zero.

#3 | Floating Pragma
Severity Location Status
Low Shib_Protocol.sol : - Pending

The current pragma Solidity directive is “^0.8.15". Contracts should be deployed with the same compiler version and flag that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.

#4 | Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
Severity Location Status
Low Shib_Protocol.sol : - Pending

We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities

#1 | Functions that are not used (dead-code)
Severity Location Status
Informational Shib_Protocol.sol : 31-34, 173-188 Pending

Remove unused functions.

#4 | Unused return values (unused-return)
Severity Location Status
Informational Shib_Protocol.sol : 707-736 Pending

Ensure that all the return values of the function calls are used.

#5 | State variables that could be declared constant (constable-states)
Severity Location Status
Informational Shib_Protocol.sol : 444 Pending

Add the `constant` attributes to state variables that never change.


Disclaimer 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. do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...) 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. 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.