Project

One World
NFTDeFi
15,000 USDC
View results
Submission Details
Severity: medium
Invalid

Burned Tokens Not Reflected in `minted` Count in `upgradeTier()`

Summary

The upgradeTier() function burns tokens from the user’s current tier as part of the upgrade process. However, the minted count for the original tier is not decremented to reflect the reduced token supply of this tie, preventing new users from joining the DAO, as the amount limit appears reached even though there is room due to the burned tokens.

Vulnerability Details

When upgradeTier() burns tokens, it does not adjust the minted count for the original tier. As a result, the protocol believes the tier has reached its maximum supply, even though tokens were burned, and prevents additional users from joining.

Example scenario:

  1. A user upgrades from tier 3 to a higher tier, resulting in two tokens being burned from tier 3.

  2. The minted count for tier 3 remains unchanged.

  3. New users are blocked from joining tier 3 because the amount limit appears reached.

Impact

Prevents new users from joining a tier despite available capacity due to burned tokens.

Tools Used

vscode

Recommendations

Modify upgradeTier() to decrement the minted count for the original tier whenever tokens are burned.

Updates

Lead Judging Commences

0xbrivan2 Lead Judge 10 months ago
Submission Judgement Published
Invalidated
Reason: Known issue

Support

FAQs

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