feeAddress in Constructor and Setter Can Result in Burned FeesThe deployer and owner initialize and update feeAddress to direct where protocol revenue is sent during withdrawFees().
Neither the constructor nor changeFeeAddress() verifies that the supplied address is non-zero. A zero address input causes subsequent fee withdrawals to send ETH directly to address(0).
Likelihood:
Accidental deployment or transaction submission with address(0) as the parameter due to input error or uninitialized variable.
Impact:
Protocol revenue is sent to address(0), permanently burning ETH with no recovery possible.
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.