Introduction
We express our gratitude to the ADI Chain team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
WADI is a wrapper contract that allows users to deposit native tokens and receive equivalent WADI tokens, which are ERC-20 compatible.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for ADI Chain |
| Audited By | Olesia Bilenka; Ivan Bondar |
| Approved By | Seher Saylik |
| Website | https://www.adi.foundation/→ |
| Changelog | 11/02/2026 - Preliminary Report |
| 13/02/2026 - Final Report | |
| Platform | ADI Network |
| Language | Solidity |
| Tags | ERC-20 |
| Methodology | https://docs.hacken.io/methodologies/smart-contracts→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for ADI Chain
- Audited By
- Olesia Bilenka; Ivan Bondar
- Approved By
- Seher Saylik
- Website
- https://www.adi.foundation/→
- Changelog
- 11/02/2026 - Preliminary Report
- 13/02/2026 - Final Report
- Platform
- ADI Network
- Language
- Solidity
- Tags
- ERC-20
Review Scope | |
|---|---|
| Repository | https://gitlab.sre.ideasoft.io/adi-foundation/adi-chain/wrapped-adi-contract→ |
| Commit | f234316 |
| Remediation commit | 3291b4f |
Review Scope
- Commit
- f234316
- Remediation commit
- 3291b4f
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
{Finding_Table?columns=title,severity,status&setting.filter.type=Vulnerability}
Documentation quality
Functional requirements are missing.
Technical description is not provided.
Code quality
Recommended Best Practices are not implemented.
The development environment is configured.
Test coverage
Code coverage of the project is 100% (branch coverage).
Deployment and basic user interactions are covered with tests.
System Overview
WADI (Wrapped ADI) is an ERC20-compliant token contract that wraps the native ADI token. The contract enables users to convert native ADI tokens into an ERC20 representation and vice versa.
Key Characteristics:
Token Standard: ERC20-compatible
Decimals: 18
Minting: 1:1 with deposited native tokens
Burning: 1:1 upon withdrawal
Total Supply: Equals contract's native token balance
Privileged roles
The system contains no privileged roles.
Potential Risks
Immutable Contract: No upgrade mechanism exists. If a critical vulnerability is discovered post-deployment, there is no way to patch the contract. Users would need to migrate to a new deployment.
No Emergency Pause: The contract cannot be halted in case of an active exploit or market emergency. All functions remain accessible at all times.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2026-1502 | Unchecked Return Value in withdraw Leads to Loss of User Funds | fixed | High | |
| F-2026-1503 | EIP-20 Deviations Render Token Incompatible with Standard Infrastructure | fixed | Medium | |
| F-2026-1504 | Absence of Emergency Recovery Mechanisms for Trapped Assets | fixed | Low | |
| F-2026-1502 | Fallback Function May Mask Integration Errors | fixed | Low | |
| F-2026-1502 | Invalid SPDX License Identifier | fixed | Observation | |
| F-2026-1500 | Lack of Error Messages in Key Operations may Result in Silent Failures | fixed | Observation | |
| F-2026-1499 | Floating Pragma | fixed | Observation |
Appendix 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://gitlab.sre.ideasoft.io/adi-foundation/adi-chain/wrapped-adi-contract→ |
| Commit | f234316 |
| Remediation commit | 3291b4f |
| Whitepaper | https://docs.adi.foundation/whitepaper→ |
| Requirements | N/A |
| Technical Requirements | N/A |
Scope Details
- Commit
- f234316
- Remediation commit
- 3291b4f
- Whitepaper
- https://docs.adi.foundation/whitepaper→
- Requirements
- N/A
- Technical Requirements
- N/A
Assets in Scope
Appendix 3. Additional Valuables
Additional Recommendations
The smart contracts in the scope of this audit could benefit from the introduction of automatic emergency actions for critical activities, such as unauthorized operations like ownership changes or proxy upgrades, as well as unexpected fund manipulations, including large withdrawals or minting events. Adding such mechanisms would enable the protocol to react automatically to unusual activity, ensuring that the contract remains secure and functions as intended.
To improve functionality, these emergency actions could be designed to trigger under specific conditions, such as:
Detecting changes to ownership or critical permissions.
Monitoring large or unexpected transactions and minting events.
Pausing operations when irregularities are identified.
These enhancements would provide an added layer of security, making the contract more robust and better equipped to handle unexpected situations while maintaining smooth operations.
Frameworks and Methodologies
This security assessment was conducted in alignment with recognised penetration testing standards, methodologies and guidelines, including the NIST SP 800-115 – Technical Guide to Information Security Testing and Assessment →, and the Penetration Testing Execution Standard (PTES) →, These assets provide a structured foundation for planning, executing, and documenting technical evaluations such as vulnerability assessments, exploitation activities, and security code reviews. Hacken’s internal penetration testing methodology extends these principles to Web2 and Web3 environments to ensure consistency, repeatability, and verifiable outcomes.