Open code423n4 opened 2 years ago
Event emissions do not pose any threat to the contract's security, especially to functions that the DAO handles
Event-related issues are of non-critical severity based on the guidelines: "Non-critical: Code style, clarity, syntax, versioning, off-chain monitoring (events etc)".
Handle
WatchPug
Vulnerability details
Across the contracts, there are certain critical operations that change critical values that affect the users of the protocol.
It's a best practice for these setter functions to emit events to record these changes on-chain for off-chain monitors/tools/interfaces to register the updates and react if necessary.
Instances include:
https://github.com/code-423n4/2021-11-fairside/blob/20c68793f48ee2678508b9d3a1bae917c007b712/contracts/network/FSDNetwork.sol#L482-L495
https://github.com/code-423n4/2021-11-fairside/blob/20c68793f48ee2678508b9d3a1bae917c007b712/contracts/network/FSDNetwork.sol#L503-L510
https://github.com/code-423n4/2021-11-fairside/blob/20c68793f48ee2678508b9d3a1bae917c007b712/contracts/network/FSDNetwork.sol#L541-L551