Miner Gold Info

minergold.io

Welcome to Chapter 1 of MinerGold.io, where every player becomes the master of their own gold mine. In this universe, every click is an opportunity to shape your journey, from extraction and storage to the lucrative sale of gold. MinerGold.io will unfold in three unique chapters, each offering a distinct experience but all connected by valuable features.

Miner Gold Logo

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.

On-Chain Insights

Smart Contract Audit

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xFd32...D2ae
Network BNB Smart Chain - Mainnet
License N/A
Compiler N/A N/A
Type N/A
Language Solidity
Onboard date 2024/01/21
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 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.

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
  • Create/Update buy/sell fees up to 15%
  • Set Router, Marketing, and Game Pool Wallet addresses
  • Withdraw BNB and any type of ERC20 tokens from the contract balance.
  • Include/Exclude wallets from fees

Note - This Audit report consists of a security analysis of the Miner Gold Token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited two token contracts for the Miner Gold team; our team did not audit other contracts associated with the project. We recommend investors to do their own research before investing.

Scope of Work

Files and details

This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.

The auditing process follows a routine series of steps:
  1. Review the specifications, sources, and instructions provided to SolidProof to ensure we understand the smart contract's size, scope, and functionality.
  2. Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  3. Specification comparison checks whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  4. Test coverage analysis determines whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  5. Symbolic execution is analyzing a program to determine what inputs cause each part of a program to execute.
  6. Based on the established industry and academic practices, recommendations, and research, best practices review smart contracts to improve efficiency, effectiveness, clarity, maintainability, security, and control.
  7. Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been intentionally or otherwise modified 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.

Findings and Audit result

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external
SmartContToken.sol
L564-566
L572-577
L953-955
L961-963
L978-980
L985-987
L992-994
L1004-1008
L1027-1031
L1049-1054
L1068-1072
L1091-1102
L1362-1364
L1373-1387
L1392-1406
L1408-1410
L1412-1414
L1416-1418
L1420-1422
L1424-1426
Description

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

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used
SmartContToken.sol
L408-420
L332-334
L345-351
L366-369
L357-360
L303-312
L397-403
L376-391
L96-98
L1183-1188
L1168-1173
L1114-1122
L1130-1158
L494-496
L891-900
L910-917
L854-861
L839-847
L830-833
L867-883
L814-816
L822-824
L242-244
L258-265
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables
SmartContToken.sol
L1304
Description

Remove unused state variables.