The _initializeFeeTypes lacks validation to ensure fee shares sum to 10,000 bps, risking future allocation errors.
A developer modifying the fees type eg. feeTypes[3] could accidentally set veRAACShare: 6000, repairShare: 3000, treasuryShare: 3000 (total = 12,000 bps). Or a governance proposal updates Insurance Fees (Type 3) but introduces a sum mismatch.
This can lead to miscalculations which will financially affect the protocol. An example:
Scenario: A governance proposal updates "Insurance Fees" (Type 3) to veRAACShare: 6000, repairShare: 3000, treasuryShare: 3000.
Total Basis Points: 6000 + 3000 + 3000 = 12,000 bps (120% of the fee).
Result: Every transaction involving insurance fees reverts due to arithmetic overflow, blocking:
User withdrawals from insurance pools.
Claims processing during market crashes.
add validation
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.