- Hacken
- Audits
- reform-dao
- [SCA] Reform DAO | ERC20 | Sep2023
Audit name:
[SCA] Reform DAO | ERC20 | Sep2023
Date:
Feb 19, 2024
Table of Content
Introduction
We express our gratitude to the Reform DAO team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
Reform operates as a Market Making investment DAO, fostering community-driven liquidity in the crypto realm through protocol-owned funds. It champions values like transparency, fairness, and inclusivity.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20; DAO |
| Timeline | 19/09/2023- 22/02/2024 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/RFRMDAO/DAO-Contracts/blob/main→ |
| Commit | 5112f38c9b91ceba45e138e5b33a5cf3698c44d9 |
Review Scope
- Commit
- 5112f38c9b91ceba45e138e5b33a5cf3698c44d9
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 Reform DAO |
| Audited By | Hacken |
| Website | http://reformdao.com/→ |
| Changelog | 26/09/2023 - Initial Review |
| 27/09/2023 - Second Review | |
| 22/02/2024 - Third Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Reform DAO
- Audited By
- Hacken
- Website
- http://reformdao.com/→
- Changelog
- 26/09/2023 - Initial Review
- 27/09/2023 - Second Review
- 22/02/2024 - Third Review
System Overview
The Reform project audit consists of an ERC20Burnable token implementation with a fixed initial supply of 1.000.000.000 tokens minted to the deployer on deployment without further minting functionality.
The attributes of the token are the following:
Name: Reform
Symbol: $RFRM
Decimals: 18
Total supply: 1 billion initial supply with burnability.
Privileged roles
The Smart Contract has no privileged roles.
Executive Summary
Documentation quality
The total Documentation quality score is 10 out of 10.
Functional Requirements are provided.
Technical Requirements are provided.
A description of the development environment is provided.
Code quality
The total Code quality score is 10 out of 10.
The development environment is configured.
Solidity Style Guides are followed.
Test coverage
Code coverage of the project is 0% (branch coverage).
For projects with less than 250 LOC (Lines of Code) the test coverage is not mandatory, and it is not accounted for in the final score.
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
No additional risks are found.
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/RFRMDAO/DAO-Contracts/blob/main→ |
| Commit | 5112f38c9b91ceba45e138e5b33a5cf3698c44d9 |
| Whitepaper | Not provided |
| Requirements | Provided→ |
| Technical Requirements | Provided→ |