BRB Cash
0x02130D419Dc3C0e73Fb9d028741ccabBd2D31062 0x0213...D31062

Static analysis Dynamic analysis Symbolic Execution SWC check

BRBC is an ERC-20 utility token used in a cross-chain ecosystem with utilities to support WEB3. By incorporating WEB3 utilities on the ETH blockchain, we are reducing the energy consumed. The goal is the ease of use and fast & environmentally friendly WEB3 interfaces.

Contract address
0x0213...D31062
Network Ethereum Mainnet
License Unlicense
Compiler v0.8.17 v0.8.17+commit.8df45f5f
Type ERC20
Language Solidity
Request date 2022/12/02
Revision date 2022/12/02
Critical
Passed
High
Passed

Owner privileges

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 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 can set high fees Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Token transfer can be locked Owner can lock user funds with owner functions.
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:

  • Include/Exclude wallets from rewards and fees
  • Set Tax, Development, and liquidity fee
  • Set Maximum Transaction percent as any arbitrary number including zero and may lock user funds

 

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

95

State variables
public

7

Total lines
of code

745

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 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.

medium Issues

Pending

#1 Issue

Fees can be set upto 100% or more

BRBToken.sol

L523,526,529

Description

The owner can set the fees to 100% or more and lock user funds

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

BRBToken.sol

L437

L627

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

BRBToken.sol

L523-525

L526-528

L529-531

L532-536

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Floating Pragma

BRBToken.sol

-

Description

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

Pending

#4 Issue

Contract doesn't import npm packages from source (like OpenZeppelin etc.)

BRBToken.sol

-

Description

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

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

BRBToken.sol

L137-150

L106-108

L109-111

L112-114

L115-120

L129-131

L132-136

L121-123

L124-128

L96-100

L101-105

L89-92

L71-76

L62-64

L77-82

L17-23

L38-43

L44-49

L30-37

L24-29

Description

Remove unused functions.

Pending

#2 Issue

Function initializing state variables (function-init-state)

BRBToken.sol

L377

L383

L385

L387

Description

Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.

Pending

#3 Issue

Unused return values (unused-return)

BRBToken.sol

L686-696

Description

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

optimization Issues

Pending

#1 Issue

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

BRBToken.sol

L381

L374

L379

L380

L376

L394

Description

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

Pending

#2 Issue

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

BRBToken.sol

L167-170

L171-175

L417-419

L420-422

L423-425

L426-428

L433-436

L437-439

L440-443

L444-448

L449-452

L453-456

L457-459

L460-462

L463-470

L471-480

L486-493

L517-519

L520-522

L537-540

L624-626

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.