Lack of event in FeeManager contract when protocol fees are changed
0xShiki
medium
Summary
The FeeManager contract is responsible for calculating and collecting fees throughout the TITLES protocol. However, there is no event emitted when the protocol fees are changed. This can make it difficult to track changes in the protocol fees.
Vulnerability Detail
In setProtocolFees function in FeeManager contract, important parameters are set and changed.
Consider adding an event to setProtocolFees function in the FeeManager contract. The ProtocolFeesChanged event can be emitted with the new protocol fees as parameters.
0xShiki
medium
Lack of event in
FeeManager
contract when protocol fees are changed0xShiki
medium
Summary
The
FeeManager
contract is responsible for calculating and collecting fees throughout the TITLES protocol. However, there is no event emitted when the protocol fees are changed. This can make it difficult to track changes in the protocol fees.Vulnerability Detail
In
setProtocolFees
function inFeeManager
contract, important parameters are set and changed.However, there is no event emitted when the protocol fees are changed, which makes it difficult to track these changes off-chain.
Impact
There is a possibility that users would not be aware of protocol fee changes.
Code Snippet
https://github.com/sherlock-audit/2024-04-titles/blob/main/wallflower-contract-v2/src/fees/FeeManager.sol#L298
Tool used
Manual Review
Recommendation
Consider adding an event to
setProtocolFees
function in theFeeManager
contract. TheProtocolFeesChanged
event can be emitted with the new protocol fees as parameters.