Audit name:
[SCA] Playbux | ERC20 | Dec2023
Date:
Apr 18, 2024
Table of Content
Introduction
We express our gratitude to the Playbux team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
Playbux is a metaverse platform that allows users to represent crypto assets and customize characters. PBUX token serves as the main currency and method of exchange for both governance of the platform as well as acquisition of all tradable virtual goods, assets and services within the Playbux metaverse.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC-20 |
| Timeline | 02/04/2024 - 03/04/2024 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/Decubate-com/smart-contracts/→ |
| Commit | 45427c9851f7db1f1f773a50cdfe44a457adf874 |
Review Scope
- Commit
- 45427c9851f7db1f1f773a50cdfe44a457adf874
Audit Summary
10/10
0%
10/10
10/10
The system users should acknowledge all the risks summed up in the risks section of the report
Document Information
This report may contain confidential information about IT systems and the intellectual property of the Customer, as well as information about potential vulnerabilities and methods of their exploitation.
The report can be disclosed publicly after prior consent by another Party. Any subsequent publication of this report shall be without mandatory consent.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for Playbux |
| Audited By | Alkautsar Fatahillah |
| Approved By | Yves Toiser |
| Website | http://playbux.co/→ |
| Changelog | 02/04/2024 - Preliminary Report |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Playbux
- Audited By
- Alkautsar Fatahillah
- Approved By
- Yves Toiser
- Website
- http://playbux.co/→
- Changelog
- 02/04/2024 - Preliminary Report
System Overview
Playbux is an ERC-20 with the following contracts:
PBUX Token — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed. A burnable feature is implemented.
It has the following attributes:
Name: Playbux
Symbol: PBUX
Decimals: 18
Total supply: 400m tokens.
Executive Summary
Documentation quality
The total Documentation Quality score is 10 out of 10.
Functional requirements are provided.
Technical description is provided.
NatSpecs are provided.
Code quality
The total Code Quality score is 10 out of 10.
The development environment is configured.
There are no code quality issues.
Test coverage
Code coverage of the project is 0% (branch coverage).
Tests are not provided (according to our methodology, tests are not mandatory for projects with less than 250 lines of codes).
Security score
Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 0 low severity issues, leading to a security score of 10 out of 10.
All identified issues are detailed in the “Findings” section of this report.
Summary
The comprehensive audit of the customer's smart contract yields an overall score of 10. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.
Risks
All the tokens are minted to a single address. The secureness of the supply depends on the secureness of key storage.
Findings
No vulnerabilities were foundAppendix 1. Severity Definitions
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, do not affect security score but can affect code quality score. |
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, do not affect security score but can affect code quality score.
Appendix 2. Scope
The scope of the project includes the following smart contracts from the provided repository:
Scope Details | |
|---|---|
| Repository | https://github.com/Decubate-com/smart-contracts/→ |
| Commit | 45427c9851f7db1f1f773a50cdfe44a457adf874 |
| Whitepaper | https://www.playbux.co/playbux-litepaper-announcement→ |
| Requirements | |
| Technical Requirements |
Scope Details
- Commit
- 45427c9851f7db1f1f773a50cdfe44a457adf874
- Requirements
- Technical Requirements