The function setFeeReceiver
does not prevent the owner from setting the _feeReceiver
as the zero address. This could result in a loss of fees, as once the zero address is set as the feeReceiver
, any fees transferred would be irrecoverable.
The setFeeReceiver
function, which is used to update the feeReceiver
address, does not have a check to prevent the new feeReceiver
from being the zero address. If the zero address is mistakenly or maliciously set as the feeReceiver
, all subsequent transfers of fees to this address would be irrecoverable, effectively being burned.
If the zero address is set as the feeReceiver
, any fees sent to the zero address are irrecoverable and effectively destroyed. This can result in a loss of income from fees.
Manual review of the smart contract code.
When updating the feeReceiver
address, add a require
statement to ensure that the new address is not the zero address. Here's an example of how you can add this check:
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.