MrBob Info

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!

MrBob Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

79.84
PoorExcellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Select the audit
Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0xa68A...bda3
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/01/29
Revision date In progress

Summary and Final Words

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 can set high fees

Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.

Token transfer can be locked

Owner can lock user funds with owner functions.

Token cannot be burned

There is no burn function within the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


Ownership Privileges:
  • Included/Exclude wallets from reward and fees
  • Set fees and liquidity percentages to any arbitrary value including 100% or more which is not recommended because it may lead to loss of user funds.
  • Set max transaction percentage to zero and lock user funds
  • Enable/Disable swap and liquify

 

We recommend investors/users to do their own research before investing

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 1 findings

Pending

#1 medium Issue
Fees can be 100% or more
Mrbob.sol
L876
Description

The owner is able to set the fees up to 100% or even more which will lead in loss of user funds and may cause some functions to revert, It is recommended to limit the maximum fees under 25% which is to be set by the owner.

low Issues | 5 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
Mrbob.sol
L776
L980
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
Mrbob.sol
L876-878
L880-882
L884-888
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Old Compiler Version
Mrbob.sol
-
Description

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.

Pending

#4 low Issue
Floating Pragma
Mrbob.sol
-
Description

The current pragma Solidity directive is “^0.6.12". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions

Pending

#5 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
Mrbob.sol
-
Description

We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
Mrbob.sol
L701
L699
L700
L695
L716
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
Mrbob.sol
L431-434
L440-444
L446-448
L451-456
L459-464
L750-752
L754-756
L758-760
L762-764
L771-774
L776-778
L780-783
L785-789
L791-794
L796-799
L801-803
L805-807
L809-816
L818-827
L835-843
L868-870
L872-874
L890-893
L976-978
Description

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

informational Issues | 3 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
Mrbob.sol
L357-378
L317-319
L327-329
L342-344
L352-355
L264-273
L291-297
L236-239
L209-211
L225-228
Description

Remove unused functions.

Pending

#2 informational Issue
Function initializing state variables (function-init-state)
Mrbob.sol
L696
L704
L707
Description

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 informational Issue
Unused return values (unused-return)
Mrbob.sol
L1075-1088
Description

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