BattleForTen
Battle For TEN is a double-currency online game. The Dragon Eggs is the currency that is used to purchase Equipment and Abilities. In addition, the official token of Battle for TEN - $BFT is also an in-game currency that can be used to purchase champions and also be used as a cryptocurrency aside from the game. There are multiple ways to earn $BFT. The daily BFT reward for 5 PvP games is the easiest way to earn $BFT tokens. Depending on the level of the champion that you are playing with $BFT rewards will change accordingly.
Owner privileges
Comments
Owner Privileges:
- Include/Exclude accounts from the reward and fee
- Set Minimum token to swap at any amount because there are no limits/range
- Set marketing wallet and enable/disable swap and liquify
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)
- 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
104
State variables
public
8
Total lines
of code
1353
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.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L1012
L1185
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1051
L1060
L1073
L1077,1081
Emit an event for critical parameter changes.
Pending
#3 Issue
Floating Pragma
-
The current pragma Solidity directive is â^0.8.0". Contracts should be deployed with the same compiler version and flag 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.)
-
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)
L20-23
L452-460
L431-439
L889-891
L905-908
L181-184
L172-176
L152-158
L140-147
L163-167
L187-190
L198-202
Remove unused functions.
Pending
#2 Issue
Function initializing state variables (function-init-state)
L925
L949
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 state variables (unused-state)
L135
Remove unused state variables.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L930
L928
L929
L924
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L259-261
L267-269
L284-286
L998-1000
L1007-1010
L1012-1014
L1016-1019
L1021-1025
L369-372
L388-391
L751-754
L760-764
L986-988
L990-992
L994-996
L1027-1030
L1032-1035
L1037-1039
L1041-1043
L1051-1058
L1073-1075
L1077-1079
L1081-1083
L1085-1088
L1090-1092
L1181-1183
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.