The removeAuctionConfig() function in the SpiceAuction contract is responsible for removing the auction configuration. However, the function emits an AuctionConfigRemoved event with incorrect parameters. This can lead to confusion and errors when tracking the removal of auction configurations, as the event does not accurately reflect the state changes.
Incorrect event emission has several potential impacts like
Tracking and Debugging: It can make it difficult to track and debug the removal of auction configurations, as the emitted event does not provide accurate information.
User Confusion: Users and developers relying on event logs for accurate and up-to-date information may face confusion and errors, affecting their interaction with the contract.
Below is the removeAuctionConfig() function, and in L131, which i also showed with @> you can see that the event was emitted wrongly
To address this issue, it is recommended to ensure that the AuctionConfigRemoved event is emitted with accurate parameters that reflect the state changes. This can be achieved by reviewing the logic and parameters passed to the event emission.
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.