Brave Arena
0x01b0E01Eb7B3bf9cF7F1c50956A7d0a69384f167 0x01b0...84f167

Static analysis Dynamic analysis Symbolic Execution SWC check

BRAVE ARENA is a PVP & PVE fighting management simulator built on BSC. Start your Fighting Adventure by minting Warrior NFTs from the market and putting them to the test! Once your warriors start winning fights, progress to higher level Arenas to challenge the Empire's greatest Champions. Your goal is to defeat all Bosses and claim victory over the Emperor Kaiser to receive the biggest BNB prize payout from the BNB Treasury.

Contract address
Network Binance Smart Chain
License Unlicense
Compiler v0.8.7 v0.8.7+commit.e28d00a7
Type N/A
Language Solidity
Request date 2023/04/28
Revision date 2023/04/28

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.

Ownership Privileges

  • Include/Exclude accounts from fees
  • Set max transaction amount but not less than 10001 tokens
  • Set Number of Tokens to swap to any arbitrary value
  • Set Treasury address
  • Set cooldown time to any arbitrary value. However, if it is set to a really high value then swap and charge function will not work properly
  • Enable/Disable swap and liquify
  • Set buy and sell fees but not more than 30%

Note - This Audit report consists of security analysis of the BraveArena smart contracts. Functional testing (or unit testing) of the contract’s logic was not included in this analysis.  We recommend everyone to do their own research.

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.



State variables


Total lines
of code


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.

low Issues


#1 Issue

Local variables shadowing (shadowing-local)





Rename the local variables that shadow another component.


#2 Issue

Missing Zero Address Validation (missing-zero-check)





Check that the address is not zero.

informational Issues


#1 Issue

Functions that are not used (dead-code)












Remove unused functions.


#2 Issue

Unused return values (unused-return)




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

optimization Issues


#1 Issue

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





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


Disclaimer 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. do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...) 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. 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.