Space Catch Info

www.spacecatch.io

The SpaceCatch designer and developer, professional gaming studio Pixelfield, aims to provide the best AR and Web3 gaming experience with today's mobile devices. SpaceCatch is implementing blockchain technology to introduce a revolutionary and sustainable play-to-earn concept, bringing a new gaming dimension and delivering the best gaming experience!

Overall Score
81.70
Poor Excellent
Space Catch 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.

TrustNet DataPulse

Smart Contract Audit

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x7B70...A01f
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/11/15
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 renounced

Contract cannot 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:
  • The minter can mint an unlimited amount of tokens after the initial deployment.

The ownership of the token is renounced, which means the owner will not be able to modify or change the state of the contract.

Note - This Audit report consists of a security analysis of the Space catch token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Space catch team. Our team did not audit other contracts associated with the project. We recommend investors 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

Resolved

#1 medium Issue
Minter can mint unlimited tokens.
CatchToken.sol
L1397-1399
Description

The minter of the contract can mint an unlimited amount of tokens after the initial deployment, which is not recommended as this can manipulate the supply of the tokens. Also, there must be a certain limit if the minter or owner wants to mint the tokens after the deployment which is not present in this scenario.

low Issues | 1 findings

Pending

#1 low Issue
Uninitialized local variables (uninitialized-local)
CatchToken.sol
L1392
Description

Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
CatchToken.sol
L798-800
L813-815
L833-837
L1076-1078
L1084-1086
L1101-1103
L1108-1110
L1115-1117
L1127-1131
L1150-1154
L1172-1177
L1191-1195
L1211-1220
Description

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

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
CatchToken.sol
L868-872
L859-861
L648-650
L1291-1307
L141-144
L152-155
L359-391
L397-402
L306-342
L348-353
L410-434
L440-445
L126-128
L133-135
L162-241
L246-252
L259-290
L295-300
L98-103
L89-93
L74-76
L81-83
L530-532
L499-503
L492-494
L467-487
Description

Remove unused functions.