Core Contracts

Regnum Aurum Acquisition Corp
HardhatReal World AssetsNFT
77,280 USDC
View results
Submission Details
Severity: medium
Invalid

Percentage allocations are wrong

Summary

Percentage allocations are wrong

Vulnerability Details

The total percentage allocations inside RAACReleaseOrchestrator are said to be 65%. This is said in the comments before the contract:

Implements vesting schedules for initial token distribution (65% of total supply)

/**
* @title RAACReleaseOrchestrator
* @author RegnumAurumAcquisitionCorp
* @notice Manages the vesting and release of RAAC tokens for various stakeholders
* @dev Implements vesting schedules for initial token distribution (65% of total supply)
* Handles different vesting schedules for team, advisors, treasury, etc.
* Ensures daily linear release over specified periods
*/

And also in the docs:

The RAACReleaseOrchestrator manages the vesting and release of RAAC tokens for various stakeholders, implementing controlled distribution of 65% of the total token supply. It provides customizable vesting schedules with different parameters for team members, advisors, treasury, and various sale participants.

However it's currently implemented that as 65.1%

// total = 65.1%
categoryAllocations[TEAM_CATEGORY] = 18_000_000 ether; // 18%
categoryAllocations[ADVISOR_CATEGORY] = 10_300_000 ether; // 10.3%
categoryAllocations[TREASURY_CATEGORY] = 5_000_000 ether; // 5%
categoryAllocations[PRIVATE_SALE_CATEGORY] = 10_000_000 ether;// 10%
categoryAllocations[PUBLIC_SALE_CATEGORY] = 15_000_000 ether; // 15%
categoryAllocations[LIQUIDITY_CATEGORY] = 6_800_000 ether; // 6.8% (5.8% + 1%)

Impact

Percentages are miscalculated and different from the desired ones.
The total supply will be distributed differently than the desired way.

Tools Used

Manual review

Recommendations

Calculate the total percentage and set it accordingly. It might require to lower one of the allocations by 0.1%

Updates

Lead Judging Commences

inallhonesty Lead Judge 7 months ago
Submission Judgement Published
Invalidated
Reason: Non-acceptable severity

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.

Give us feedback!