The increase
function in the veRAACToken
contract does not validate that newly minted veRAACTokens stay within the defined MAX_TOTAL_SUPPLY
limit. Unlike other minting paths (e.g., lock()
), this oversight allows an attacker to inflate the total veRAACToken supply beyond the 100 million cap.
The increase
function bypasses the supply cap by minting additional veRAACTokens without verifying the new total supply remains within the defined MAX_TOTAL_SUPPLY
limit. This vulnerability violates the supply control guarantee, undermines the scarcity of veRAACTokens, and compromises the integrity of the governance mechanism. A malicious actor can exploit this by repeatedly calling the increase
function with valid inputs; each call mints extra tokens until the global veRAACToken supply exceeds the maximum allowed, breaking the contract’s economic rules.
This vulnerability has a critical impact as it destroys the fixed supply guarantee, which is essential for preserving token scarcity and accurate governance weight.
The issue manifests through a straightforward execution path in the increase
function, making it highly probable an attacker will exploit it. Excess tokens issued will distort voting power and reward distributions across the ecosystem.
Manual Review
Implement a check within the increase
function to ensure the additional minting does not cause the total supply of veRAACTokens to exceed MAX_TOTAL_SUPPLY
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.