BRB Cash Info

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.

BRB Cash Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

86.60
PoorExcellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x0213...1062
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/12/02
Revision date In progress

Summary and Final Words

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

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


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

 

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 1 findings

Pending

#1 medium 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 | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
BRBToken.sol
L437
L627
Description

Rename the local variables that shadow another component.

Pending

#2 low 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 low 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 low 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

optimization Issues | 2 findings

Pending

#1 optimization 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 optimization 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.

informational Issues | 3 findings

Pending

#1 informational 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 informational 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 informational Issue
Unused return values (unused-return)
BRBToken.sol
L686-696
Description

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