The collectFee() function declares a FeeCollected() event but never emits it, reducing transparency and making it difficult to track when fees are collected.
The collectFee() function should emit a FeeCollected() event after successfully collecting fees to provide transparency and enable off-chain monitoring of fee collection activities.
Likelihood:
Occurs every time collectFee() is called successfully
Affects all fee collection operations throughout the protocol lifecycle
Impact:
Reduced transparency for users and monitoring systems
Difficulty in tracking fee collection history and frequency
Inconsistent event emission pattern compared to other protocol functions
Potential compliance issues for protocols requiring audit trails
The below sets up a fee cllection scenario, then tries to collect fees but does not emit an event:
Recommend implementing an event emission in the collectFee() function after successfully collecting fees to provide transparency and enable off-chain monitoring of fee collection activities.
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.