Shibosu
0x38e3b07D607dEF629b4f3f46a0082006fdd6CDa2 0x38e3...d6CDa2

Static analysis Dynamic analysis Symbolic Execution SWC check

Dedicated to the journey of Kabosu… We bring to you the biggest meme of 2023 SHIBOSU. Kabosu inspired all of the biggest dog meme hype, shit coins like dogecoin, Shiba Inu, and now SHIBOSU. SHIBUSO will aim to create the same inspirational journey bringing together all the dog meme communities and showering them with the amazing journey Kabosu created for us over 13 years ago.

Contract address
0x38e3...d6CDa2
Network Ethereum Mainnet
License MIT
Compiler v0.8.10 v0.8.10+commit.fc410830
Type N/A
Language Solidity
Request date 2023/01/10
Revision date 2023/01/10
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

No critical issues found The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.
Contract owner cannot mint It is not possible to mint new tokens.
Contract owner cannot blacklist addresses. It is not possible to lock user funds by blacklisting addresses.
Contract owner cannot set high fees The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
Contract cannot be locked Owner cannot lock any user funds.
Token cannot be burned There is no burn function within the contract.
Ownership is renounced Contract cannot be manipulated by owner functions.
Comments

Ownership Privileges:

  • Not Applicable, as the ownership has been renounced

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.

Functions
public

83

State variables
public

31

Total lines
of code

1602

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)

Shibosu.sol

L1137

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

Shibosu.sol

L1194-1209

L1211-1217

L1219-1225

L1239-1249

L1251-1261

L1532-1548

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Zero Address Validation (missing-zero-check)

Shibosu.sol

L1286

L1294

Description

Check that the address is not zero.

Pending

#4 Issue

Dangerous usage of `tx.origin` (tx-origin)

Shibosu.sol

L1305-1443

Description

Do not use `tx.origin` for authorization.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

Shibosu.sol

L29-31

L497-512

L672-674

L770-779

L730-732

L796-805

L747-756

L601-607

L643-648

L655-660

L626-636

L614-619

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

State variables that could be declared constant (constable-states)

Shibosu.sol

L1052

Description

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

Pending

#2 Issue

Public function that could be declared external (external-function)

Shibosu.sol

L87-89

L95-98

L284-286

L292-294

L309-311

L335-338

L343-345

L354-357

L372-386

L400-403

L419-427

L1268-1278

L1299-1301

Description

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.