MrBob
Mr. Bob is a Web3 community tha's passionate about Gamefi and Web3 culture, providing gamers with an exciting virtual hangout where you can network with other Web 3 gamers just like you. Networks are the key to success in any Web3 community or field for that matter and Mr. Bob provides its users with an easy way to network and chat with other gamers from around the world. On Mr. Bob, users can engage with others and receive Web3 metaverse tokens in the process! All members of the platform have access to their native token, $MBOB. Holding this token allows you to vote on which developersubmitted game will receive funding through a grant system enabled by Mr. Bob's core team. This ensures that everyone has an equal say in what games should be funded and developed further, taking Web3 gaming to the next level!
Owner privileges
Comments
Ownership Privileges:
- Included/Exclude wallets from reward and fees
- Set max transaction percentage to zero and lock user funds
- Enable/Disable swap and liquify
The ownership is renounced for now but the owner can regain ownership in this contract so be aware of it. It can be done in the following steps:
- Call lock function to set _previousOwner to the own address
- Call unlock function to get ownership back
- Transfer/renounce ownership
- Call unlock function to get ownership back
Make sure to set the _previousOwnership back to address zero after using the unlock function.
We recommend investors/users to 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)
- 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
98
State variables
public
6
Total lines
of code
868
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)
L498
L705
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L598-601
L603-606
L608-613
Emit an event for critical parameter changes.
Pending
#3 Issue
Old Compiler Version
-
The contract uses an old compiler version (^0.6.12) and we don't recommend using it because old versions tend to have known vulnerabilities that may get exploited in the future.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L117-134
L100-102
L104-106
L108-110
L112-115
L82-91
L92-98
L75-78
L60-62
L64-67
Remove unused functions.
Pending
#2 Issue
Function initializing state variables (function-init-state)
L418
L426
L429
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 return values (unused-return)
L800-813
Ensure that all the return values of the function calls are used.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L423
L421
L422
L417
L438
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L159-162
L164-168
L170-172
L174-179
L181-186
L472-474
L476-478
L480-482
L484-486
L493-496
L498-500
L502-505
L507-511
L513-516
L518-521
L523-525
L527-529
L531-538
L540-549
L557-565
L590-592
L594-596
L615-618
L701-703
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.