Audit name:
[SCA] PlayMind / Token / Dec2024
Date:
Dec 24, 2024
Table of Content
Introduction
We express our gratitude to the Spielworks team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
PlayMind Token is an ERC-20 token solution that implements ERC20Capped library of OpenZeppelin.
The latest vesion of report that went through a security assessment is deployed at the address 0x4d3557cf9e3D47A665aecB28BBDc10018433A176.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for PlayMind |
| Audited By | Turgay Arda Usman |
| Approved By | Grzegorz Trawinski |
| Website | http://spielworks.com/→ |
| Changelog | 09/12/2024 - Preliminary Report |
| 18/12/2024 - Second Report | |
| 20/12/2024 - Final Report | |
| Platform | Ethereum |
| Language | Solidity |
| Tags | ERC20 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for PlayMind
- Audited By
- Turgay Arda Usman
- Approved By
- Grzegorz Trawinski
- Website
- http://spielworks.com/→
- Changelog
- 09/12/2024 - Preliminary Report
- 18/12/2024 - Second Report
- 20/12/2024 - Final Report
- Platform
- Ethereum
- Language
- Solidity
- Tags
- ERC20
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Repository | https://etherscan.io/address/0xa763e48fa0e6a4dfdf91152b774792b64d158177→ |
| Commit | n/a |
Review Scope
- Commit
- n/a
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
Documentation quality
Functional requirements are provided.
Technical description is not provided.
Code quality
The code mostly follows best practices and style guides.
For more information see informational and low findings.
The development environment is not configured.
Test coverage
Code coverage of the project is 100.00% (branch coverage):
Deployment and basic user interactions are not covered with tests.
Negative cases coverage is missed.
The active LoC is less than 250, so unit tests are not mandatory.
System Overview
PlayMind is a simple ERC20 token with the following contracts:
PlayMindToken — simple ERC-20 token with burn feature.
It has the following attributes:
Name: PlayMind
Symbol: PLAI
Decimals: 18
Total supply: 40B tokens
Potential Risks
The project concentrates minting tokens in a single address, raising the risk of fund mismanagement or theft, especially if key storage security is compromised.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2024-7745 | Publicly Accessible BurnFrom Function | fixed | Low | |
| F-2024-7548 | Lack of Two-Step Ownership Pattern | fixed | Observation | |
| F-2024-7547 | renounceOwnership() Can Be Called Accidentally | fixed | Observation | |
| F-2024-7546 | Floating Pragma | fixed | Observation |
Identify vulnerabilities in your smart contracts.
Appendix 1. Definitions
Severities
When auditing smart contracts, Hacken is using a risk-based approach that considers Likelihood, Impact, Exploitability and Complexity metrics to evaluate findings and score severities.
Reference on how risk scoring is done is available through the repository in our Github organization:
Severity | Description |
|---|---|
Critical | Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation. |
High | High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation. |
Medium | Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category. |
Low | Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution. |
Severity
- Critical
Description
- Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.
Severity
- High
Description
- High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.
Severity
- Medium
Description
- Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.
Severity
- Low
Description
- Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution.
Potential Risks
The "Potential Risks" section identifies issues that are not direct security vulnerabilities but could still affect the project’s performance, reliability, or user trust. These risks arise from design choices, architectural decisions, or operational practices that, while not immediately exploitable, may lead to problems under certain conditions. Additionally, potential risks can impact the quality of the audit itself, as they may involve external factors or components beyond the scope of the audit, leading to incomplete assessments or oversight of key areas. This section aims to provide a broader perspective on factors that could affect the project's long-term security, functionality, and the comprehensiveness of the audit findings.
Appendix 2. Scope
The scope of the project includes the following smart contracts from the provided repository:
Scope Details | |
|---|---|
| Repository | https://etherscan.io/address/0xa763e48fa0e6a4dfdf91152b774792b64d158177→ |
| Commit | n/a |
| Whitepaper | https://spielworks.gitbook.io/spielworks-whitepaper→ |
| Requirements | https://spielworks.gitbook.io/spielworks-whitepaper→ |
| Technical Requirements | https://spielworks.gitbook.io/spielworks-whitepaper→ |
Scope Details
- Commit
- n/a
- Technical Requirements
- https://spielworks.gitbook.io/spielworks-whitepaper→
Assets in Scope
Appendix 3. Additional Valuables
Additional Recommendations
The smart contracts in the scope of this audit could benefit from the introduction of automatic emergency actions for critical activities, such as unauthorized operations like ownership changes or proxy upgrades, as well as unexpected fund manipulations, including large withdrawals or minting events. Adding such mechanisms would enable the protocol to react automatically to unusual activity, ensuring that the contract remains secure and functions as intended.
To improve functionality, these emergency actions could be designed to trigger under specific conditions, such as:
Detecting changes to ownership or critical permissions.
Monitoring large or unexpected transactions and minting events.
Pausing operations when irregularities are identified.
These enhancements would provide an added layer of security, making the contract more robust and better equipped to handle unexpected situations while maintaining smooth operations.