The protocol currently lacks a pausing mechanism for several user-facing functions. This functionality is critical for maintaining control over the protocol's operations during a paused state. Without the ability to pause specific functions, critical operations may continue even when the protocol should be halted, leading to potential security vulnerabilities, financial losses, or other unintended consequences. It is crucial to implement a whenNotPaused
modifier in all user-facing functions to prevent any operations from occurring during a paused state.
Functions that should be paused include:
Mannually review
Add whenNotPaused
modifier to all user-facing functions to prevent any operations when the protocol is paused. This will ensure that no user interactions can occur during a paused state, protecting the protocol from potential vulnerabilities or unintended consequences.
I believe this is informational and non-acceptable severity because: - A single pause on withdraw to be sufficient to pause the markets during times of emergencies, given that is the only function where collateral/point tokens/native ETH can be pulled from market transactions. - Every tadle market place can be switched offline by the admin via [`updateMarketPlaceStatus`](https://github.com/Cyfrin/2024-08-tadle/blob/04fd8634701697184a3f3a5558b41c109866e5f8/src/core/SystemConfig.sol#L160-L171) and is checked in market actions via [`checkMarketPlaceStatus`](https://github.com/Cyfrin/2024-08-tadle/blob/04fd8634701697184a3f3a5558b41c109866e5f8/src/libraries/MarketPlaceLibraries.sol#L54-L67) to be online. This prevents many major market actions including the creation, listing and settlement of offers.
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.