Audit name:
[SCA] DYOR | Token | Jan2025
Date:
Jan 17, 2025
Table of Content
Introduction
We express our gratitude to the DYOR team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
Dyor Exchange is a decentralized platform that simplifies on-chain investing; where the Dyor token enhances this ecosystem by granting investors access to premium features, such as advanced analytics and reduced platform fees.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for DYOR |
| Audited By | Adam Idarrha |
| Approved By | Oleksii Haponiuk |
| Website | https://dyor.exchange/→ |
| Changelog | 17/01/2025 - Preliminary Report |
| Platform | Base |
| Language | Solidity |
| Tags | Fungible Token, ERC20 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for DYOR
- Audited By
- Adam Idarrha
- Approved By
- Oleksii Haponiuk
- Website
- https://dyor.exchange/→
- Changelog
- 17/01/2025 - Preliminary Report
- Platform
- Base
- Language
- Solidity
- Tags
- Fungible Token, ERC20
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Repository | https://github.com/Decubate-com/smart-contracts→ |
| Commit | 416f453 |
Review Scope
- Commit
- 416f453
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 provided.
Code quality
The code mostly conforms with the Solidity Style Guide.
Test coverage
Code coverage of the project is 0% (branch coverage):
Tests are not mandatory for project with LoC less than 250.
System Overview
DYOR— simple ERC-20 token that mints all initial supply to an address. Additional minting is not allowed, with burnable features.
It has the following attributes:
Name: Do Your Own Research
Symbol: DYOR
Decimals: 18
Total supply: 800 million tokens.
Potential Risks
Centralization risk: The project centralizes token minting to a single address, heightening the risk of fund mismanagement or theft, particularly if key storage is compromised.
Findings
No vulnerabilities were foundAppendix 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://github.com/Decubate-com/smart-contracts→ |
| Commit | 416f453588de98adc7824e88241edb9a4d396e15 |
| Whitepaper | |
| Requirements | |
| Technical Requirements |
Scope Details
- Commit
- 416f453588de98adc7824e88241edb9a4d396e15
- Whitepaper
- Requirements
- Technical Requirements