BRO
0x70726f28ec6f462CaC1Fc7c60Cc25281c72630f9 0x7072...2630f9

Static analysis Dynamic analysis Symbolic Execution SWC check

Navigate the dynamic world of cryptocurrency with Bro Signals – the ultimate signal bot that transforms volatility into opportunity. Designed for both novice traders and seasoned investors, Bro Signals harnesses the power of advanced analytics to provide real-time trading alerts, empowering you to make informed decisions with confidence.

Contract address
0x7072...2630f9
Network Ethereum Mainnet
License MIT
Compiler v0.8.18 v0.8.18+commit.87f61d96
Type N/A
Language Solidity
Request date 2023/11/22
Revision date 2024/03/19
Critical
Passed
High
Passed
Medium
1 Issue
Low
2 Issues
Informational
Passed
Optimization
1 Issue

Owner privileges

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

  • Any arbitrary address can claim the stuck tokens to the Fee receiver wallet.
  • The owner can enable trading only once.
  • The owner can manually redeem tokens.
  • The owner can lock the receiver details in the contract.
  • The owner can update the minimum swap amount of not less than 5%.
  • The owner can enable/disable the fee setting in the contract.
  • The owner can change the status of revenue share settings in the contract.
  • The owner can enable/disable swapping.
  • The owner can update the fee receiver in the contract.
  • The owner can update the revenue share distributor in the contract.
  • The owner can update the LP pair in the contract.
  • The owner can update the router address in the contract.
  • The owner can exempt wallets from fees.
  • The owner can exempt the account for revenue share.
  • The owner can buy back tokens to not more than five at a time.

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

54

State variables
public

25

Total lines
of code

2250

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

Liquidity is added to externally owned address.

BRO.sol

L1314-1324

Description

The contract's liquidity is automatically added to the 'Fee receiver' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.

low Issues

Pending

#1 Issue

Floating pragma solidity version

BRO.sol

L24

Description

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

Pending

#2 Issue

Missing 'require' check

BRO.sol

L1150-1184

Description

Any arbitrary address can withdraw the stuck tokens from the contract to the ‘projectOwner’ wallet as this can increase the unnecessary transactions in the contract. Add a ‘require’ check so that only the limited address can access this functionality in the contract.

optimization Issues

Pending

#1 Issue

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

BRO.sol

L785-787

L1832-1834

L1843-1845

L1856-1858

L1894-1898

L1927-1934

L1947-1956

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.