The getBoostMultiplier
function contains a critical mathematical error where any non-zero userBoost.amount
results in MAX_BOOST
. The division operation incorrectly normalizes values, leading to constant maximum returns.
Problematic Implementation:
Issue: The calculation effectively divides a value by itself after scaling, resulting in a constant maximum multiplier for any non-zero input.
Maximum boost applied regardless of actual qualification
Inequitable reward distribution
Misleading boost indicators affecting user decisions
Manual code review
Solidity static analysis
Implement proper boost calculation formula considering actual user metrics
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.