The event emitted in the constructor could lead to chasing down the wrong leads via event emissions.
The constructor of the Governance contract emits an incorrect event when validating the veToken and timelock addresses. The current implementation uses the InvalidTimelockAddress event for both the veToken and timelock address checks, which is misleading and could cause confusion during debugging or auditing.
In the constructor, the following code is used to validate the addresses:
Using the wrong event for the veToken address validation can lead to misunderstandings about which address is invalid, complicating troubleshooting and potentially leading to incorrect assumptions about the contract's behavior.
Define a separate event or revert reason for the veToken address validation to clearly distinguish between the two checks. For example, use InvalidVeTokenAddress for the veToken address 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.