- Hacken
- Audits
- dexe-network
- [SCA] DeXe | Token sales | Sep2020
Audit name:
[SCA] DeXe | Token sales | Sep2020
Date:
Sep 23, 2020
Table of Content
Introduction
We express our gratitude to the DeXe Network team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
DeXe Network is a platform for Defi asset management.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for DeXe Network |
| Audited By | Hacken |
| Changelog | 20/09/2020 - Initial Audit |
| 24/09/2020 - Second Review | |
| Platform | EVM |
| Language | Solidity |
| Tags | Token, Token-sales, Staking |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for DeXe Network
- Audited By
- Hacken
- Changelog
- 20/09/2020 - Initial Audit
- 24/09/2020 - Second Review
- Platform
- EVM
- Language
- Solidity
- Tags
- Token, Token-sales, Staking
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Audit Archive File | dexe-8ca55a54680edb118108384318f1867caf65565b.zip |
| SHA256 Checksum | c3b6df51f4b88bc7f518c425786a518548d89052153a65310058f7f74057ff18 |
Review Scope
- Audit Archive File
- dexe-8ca55a54680edb118108384318f1867caf65565b.zip
- SHA256 Checksum
- c3b6df51f4b88bc7f518c425786a518548d89052153a65310058f7f74057ff18
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
System Overview
Conclusion
Smart contracts within the scope was manually reviewed and analyzed with static analysis tools. For the contract high level description of functionality was presented in As-is overview section of the report.
Audit report contains all found security vulnerabilities and other issues in the reviewed code.
Security engineers found 1 medium and 1 low severity issue during the initial audit. All the issues have been fixed before the secondary audit.
The code is well-tested and works as described in the whitepaper.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2020-1920 | Improper Limit | fixed | Medium | |
| F-2020-1921 | Unused Field | fixed | Low |
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 | |
|---|---|
| Archive Name | dexe-8ca55a54680edb118108384318f1867caf65565b.zip |
| SHA256 Checksum | c3b6df51f4b88bc7f518c425786a518548d89052153a65310058f7f74057ff18 |
| Whitepaper | Not provided |
| Requirements | Not provided |
| Technical Requirements | Not provided |
Scope Details
- Archive Name
- dexe-8ca55a54680edb118108384318f1867caf65565b.zip
- SHA256 Checksum
- c3b6df51f4b88bc7f518c425786a518548d89052153a65310058f7f74057ff18
- Whitepaper
- Not provided
- Requirements
- Not provided
- Technical Requirements
- Not provided