- Hacken
- Audits
- horse-racing
- [SCA] Horse Racing | ERC20 | Apr2023
Audit name:
[SCA] Horse Racing | ERC20 | Apr2023
Date:
Apr 13, 2023
Table of Content
Introduction
We express our gratitude to the Horse Racing team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
Horse Racing is a blockchain-based P2E game about horse racing. The game creates a whole world dedicated to horses, and graphic design will attract the player no less strongly than the real world. FEED token is the core cryptocurrency of Horse Racing
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20 |
| Timeline | 05/04/2023 - 12/04/2023 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/GotBit/nexus-derby→ |
| Commit | c12e39605e8941095fd598d69d9ffcdbe352dfeb |
Review Scope
- Repository
- https://github.com/GotBit/nexus-derby→
- Commit
- c12e39605e8941095fd598d69d9ffcdbe352dfeb
Audit Summary
10/10
100%
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 Horse Racing |
| Audited By | Hacken |
| Changelog | 12/04/2023 – Initial Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Horse Racing
- Audited By
- Hacken
- Changelog
- 12/04/2023 – Initial Review
System Overview
Token — simple ERC-20 token that mints all of its initial supply and sends it to a specific address. Additional minting is not allowed. It has the following attributes:
Name: Specified in the constructor (name).
Symbol: Specified in the constructor (symbol).
Decimals: 18 (inherited from the ERC20 standard).
Total supply: 5,000,000,000 tokens.
Executive Summary
Documentation quality
The total Documentation quality score is 10 out of 10.
Functional requirements are provided.
Code quality
The total Code quality score is 10 out of 10.
Environment is configured.
Test coverage
Code coverage of the project is 100% (branch coverage).
Tests are provided.
Security score
Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 0 low severity issues. Out of these, 0 issues have been addressed and resolved, 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 specific address.
Appendix 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/GotBit/nexus-derby→ |
| Commit | c12e39605e8941095fd598d69d9ffcdbe352dfeb |
| Whitepaper | Not provided |
| Requirements | Provided |
| Technical Requirements | Not provided |
Scope Details
- Repository
- https://github.com/GotBit/nexus-derby→
- Commit
- c12e39605e8941095fd598d69d9ffcdbe352dfeb
- Whitepaper
- Not provided
- Requirements
- Provided
- Technical Requirements
- Not provided