The excessTokens variable in tick() lacks an upper bound, risking over-accumulation from high emissions or delays. This medium-impact, low-likelihood issue could skew economics or exceed pool capacity, though limited by raacToken minting constraints, potentially causing distribution issues.
excessTokens grows unchecked. Example:
tick() with emissionRate = 2000e18 / 7200 (2000 RAAC/day), delayed 30 days (216000 blocks).
excessTokens += 432000e18 (432K RAAC, $432K at 1M pool), exceeding capacity.
Excess $432K disrupts economics or reverts.
Excess RAAC (e.g., $432K) could distort value or cause failures, a medium-impact issue. The low likelihood depends on extreme delays or misconfigurations, but the absence of a cap poses a latent risk to stability.
Manual Code Review: To confirm missing cap on excessTokens.
Cap excessTokens:
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.