Core Contracts

Summary

The RAACReleaseOrchestrator contract documentation states that the vesting schedules cover 65% of the total token supply. However, the category allocations defined in the contract add up to 65.1%, creating an inconsistency between the documented intent and the actual numbers.

Vulnerability Details

Within the contract, the following category allocations are initialized:

• TEAM_CATEGORY: 18,000,000 tokens (18%)

• ADVISOR_CATEGORY: 10,300,000 tokens (10.3%)

• TREASURY_CATEGORY: 5,000,000 tokens (5%)

• PRIVATE_SALE_CATEGORY: 10,000,000 tokens (10%)

• PUBLIC_SALE_CATEGORY: 15,000,000 tokens (15%)

• LIQUIDITY_CATEGORY: 6,800,000 tokens (6.8% – noted as 5.8% + 1%)

When summed, these allocations total 65,100,000 tokens, or 65.1% of the total supply (assuming a 100 million token supply). This conflicts with the contract comment at line 16, which specifies that the vesting schedules are for 65% of the total supply.

Impact

• Documentation Confusion: The mismatch between the documented percentage (65%) and the actual sum (65.1%) can lead to confusion among auditors, developers, and stakeholders regarding the true tokenomics.

• *otential Misconfiguration: If the total supply or allocation percentages were intended to be precise, even a 0.1% discrepancy might indicate an error in calculation or configuration, which could have downstream effects on vesting, token distribution, and overall protocol economics.

Tools Used

• Manual code review

Recommended Mitigation

• Review and Adjust Allocations: Re-calculate the intended token allocations for each category to ensure they sum precisely to 65% of the total supply if that is the target.

• Update Documentation: Alternatively, update the contract documentation to accurately reflect the actual allocations (i.e., 65.1% of the total supply) if the current figures are correct.