- Hacken
- Audits
- ithaca-protocol
- [SCA] Ithaca Protocol | Token | Dec2024
Audit name:
[SCA] Ithaca Protocol | Token | Dec2024
Date:
Dec 12, 2024
Table of Content
Introduction
We express our gratitude to the Ithaca Protocol team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
ITHACA is a simple ERC-20 token which mints all the total supply to the deployer. The contract also implements burnable functionalities.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for Ithaca Protocol |
| Audited By | Alkautsar Fatahillah |
| Approved By | Yves Toiser |
| Website | https://www.ithacaprotocol.io/→ |
| Changelog | 09/12/2024 - Final Report |
| Platform | BSC |
| Language | Solidity |
| Tags | ERC-20, BEP-20 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Ithaca Protocol
- Audited By
- Alkautsar Fatahillah
- Approved By
- Yves Toiser
- Changelog
- 09/12/2024 - Final Report
- Platform
- BSC
- Language
- Solidity
- Tags
- ERC-20, BEP-20
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Repository | https://github.com/Decubate-com/smart-contracts→ |
| Commit | 2a8d75e05af76bc09dcef561562ecda541eafb2e |
Review Scope
- Commit
- 2a8d75e05af76bc09dcef561562ecda541eafb2e
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 adheres to Solidity Style Guide's recommendation.
The code code adheres to best practises in terms of readability.
Although configured, the development environment is broken due to a compiler usage that do not match the solidity version required by the contract. In order to evaluate the correct compilation of the contract, the code has been tested within a new development environment built for this specific purpose.
Test coverage
Code coverage of the project is 100% (branch coverage).
Tests are not mandatory below 250 lines of code.
System Overview
ITHACA — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed. The contract additionally implements burnable functionalities.
It has the following attributes:
Name: Ithaca Protocol
Symbol: ITHACA
Decimals: 18
Total supply: 1B tokens.
Privileged roles
No privileged roles are detected.
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 | 2a8d75e05af76bc09dcef561562ecda541eafb2e |
| Whitepaper | https://docs.ithacaprotocol.io/docs/→ |
| Requirements | |
| Technical Requirements |
Scope Details
- Commit
- 2a8d75e05af76bc09dcef561562ecda541eafb2e
- Whitepaper
- https://docs.ithacaprotocol.io/docs/→
- Requirements
- Technical Requirements