Red Bonk
0xB5b5308b92a7AEAd4C282e2F09e6d6dff32d881b 0xB5b5...2d881b

Static analysis Dynamic analysis Symbolic Execution SWC check

REDBONK (‘RBONK’) is a digital token deployed on the Binance Smart Chain, adhering to the BEP20 standard. RBONK holds no intrinsic value, utility, or functions and does not promise any financial returns, profits, interest, or dividends.

Contract address
0xB5b5...2d881b
Network Binance Smart Chain
License None
Compiler v0.4.24 v0.4.24+commit.e67f0147
Type N/A
Language Solidity
Request date 2024/02/28
Revision date 2024/02/28
Critical
Passed
High
Passed
Medium
Passed
Informational
Passed

Owner privileges

No crucial 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 not renounced Contract can be manipulated by owner functions.
Comments

Ownership Privileges

  • The owner can claim stuck tokens from the contract including the contract's tokens.

Note - This Audit report consists of a security analysis of the Red Bonk 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 Red Bonk 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)
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

24

State variables
public

6

Total lines
of code

212

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

Missing Zero Address Validation (missing-zero-check)

RedBonk.sol

L75

Description

Check that the address is not zero.

Pending

#2 Issue

Old compiler version

RedBonk.sol

L6

Description

Adding the constant latest version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Pending

#3 Issue

Missing 'require' error message

RedBonk.sol

L71

L79

Description

Adding the error message while using the 'require' check inside the function or a modifier in the contract is recommended.

Pending

#4 Issue

Missing visibility

RedBonk.sol

L97

L98

Description

It is recommended to use access modifiers such as 'public,' 'private,' or 'internal' during the declaration or initialization of a state variable or a mapping in the contract.

optimization Issues

Pending

#1 Issue

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

RedBonk.sol

L21-24

L25-28

L36

L37

L38

L39

L40

L41

L53

L75-77

L78-83

L190-195

L201-203

L209-211

Description

Use the `external` attribute for functions never called from the contract.

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.