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.
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:
A user upgrades from tier 3 to a higher tier, resulting in two tokens being burned from tier 3.
The minted
count for tier 3 remains unchanged.
New users are blocked from joining tier 3 because the amount
limit appears reached.
Prevents new users from joining a tier despite available capacity due to burned tokens.
vscode
Modify upgradeTier()
to decrement the minted
count for the original tier whenever tokens are burned.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.