Gov Token - OpenEden

1. Introduction

OpenEden engaged Halborn to conduct a security assessment of their smart contracts from July 1st, 2025 to July 4th, 2025. The security assessment was scoped to the smart contracts provided in the OpenEdenHQ/usdo.tge.audit Github repository provided to Halborn. Further details can be found in the Scope section of this report.

2. Assessment Summary

Halborn was provided 4 (four) days for the engagement, and assigned one full-time security engineer to review the security of the smart contracts in scope. The engineer is a blockchain and smart contract security expert with advanced penetration testing and smart contract hacking skills, and deep knowledge of multiple blockchain protocols.
The purpose of the assessment is to:

• Identify potential security issues within the smart contracts.

• Ensure that smart contract functionality operates as intended.

In summary, Halborn identified some improvements to reduce the likelihood and impact of risks, which were partially addressed by the OpenEden team. The main ones were the following: 

• Prevent allocation overwrites after vesting completion by adding timestamp validation to setAllocations().

• Add zero-address validation in Eden.initialize to prevent token deployment without a controllable admin.

• Remove the unnecessary _update override in Eden.sol to optimize bytecode size and reduce deployment costs.

• Remove the redundant decimals override in XEden.sol that duplicates inherited ERC20Upgradeable behavior.

• Add treasury percentage validation in EdenPublicAirdropVesting initializer to prevent deployment with invalid values.

• Complete NatSpec documentation for all externally callable functions to accelerate audits and integration processes.

3. Caveats

The commit 5961045, which introduces the new feature, phased distribution of forfeited tokens between stability mechanisms and treasury management, is outside the scope of this assessment.

4. Test Approach and Methodology

Halborn employed a combination of manual, semi-automated, and automated security testing to balance efficiency, timeliness, practicality, and accuracy within the scope of this assessment. Manual testing is essential for uncovering flaws in logic, process, and implementation, while automated techniques enhance code coverage and quickly identify deviations from security best practices. The following phases and tools were utilized throughout the assessment:

• Research into the architecture and purpose of the smart contracts.

• Manual code review and walkthrough of the smart contracts.

• Manual assessment of critical Solidity variables and functions to identify potential vulnerability classes.

• Manual testing using custom scripts.

• Static security analysis of the scoped contracts and imported functions using Slither.

• Local deployment and testing with Foundry.