Space Catch
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!
Owner privileges
Comments
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.
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
34
State variables
public
2
Total lines
of code
1400
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.
medium Issues
Resolved
#1 Issue
Minter can mint unlimited tokens.
L1397-1399
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
Pending
#1 Issue
Uninitialized local variables (uninitialized-local)
L1392
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
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
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
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
Use the `external` attribute for functions never called from the contract.
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.