Brazil Fan Token
0xF4d1C0a6410149b555107d01De67563F1FC62BCd 0xF4d1...C62BCd

Static analysis Dynamic analysis Symbolic Execution SWC check

Brazil Fan Tokens ($BRA) are digital assets built on Binance Smart Chain. They exist in limited numbers, and their ownership is logged forever on the blockchain. Holding just one $BRA Fan Token unlocks exclusive perks and benefits for FC Nation Brazil Team fans, such as the ability to vote in community decisions and VIP access to matches and events. Fan Tokens don’t expire, and they don’t require an annual renewal fee. Holding $BRA Fan Tokens give you access to all the attached rewards and benefits.

Contract address
0xF4d1...C62BCd
Network Binance Smart Chain
License Unlicense
Compiler v0.8.17 v0.8.17+commit.8df45f5f
Type ERC20
Language Solidity
Request date 2022/11/01
Revision date In progress
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

No critical 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

  • Beware of the "isAuth" logic. When the owner renounce the ownership the devWallet is still able to change things in the contract
    • excludeFromReward/IncludeInReward
    • enableTrading
    • excludeFromFee/IncludeFromFee
  • Owner is able to take out the natives from the contract

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

41

State variables
public

10

Total lines
of code

670

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

Local variables shadowing (shadowing-local)

BRA.sol

L242

L483

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Access Control (events-access)

BRA.sol

L647-650

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Events Arithmetic (events-maths)

BRA.sol

L652-655

Description

Emit an event for critical parameter changes.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

BRA.sol

L36-39

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

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

BRA.sol

L139

Description

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

Pending

#2 Issue

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

BRA.sol

L60-62

L64-67

L221-223

L225-227

L229-231

L233-235

L242-244

L246-249

L251-263

L265-268

L270-279

L281-284

L286-288

L290-303

L340-342

L344-346

L348-350

L664-667

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.