No event emission while changing states from pausing to unpausing or vice-versa
Summary
The contract's pause/unpause function does not emit an event when transitioning between paused and unpaused states. This can lead to difficulties in tracking and monitoring state changes, reducing transparency and making it harder for users and developers to detect when a critical function is temporarily disabled or re-enabled.
Vulnerability Detail
In the code, the pause_unpause.rs file, found in the WOOFi_Solana program, handles the pausing and unpausing of contract functionality. However, there is no event emitted when the contract's state transitions between paused and unpaused modes. This makes it difficult for off-chain tools and users to track these critical state changes efficiently.
The absence of emitted events for pausing and unpausing operations can lead to reduced transparency, which affects the ability of users and off-chain services to monitor critical contract states effectively. This could result in delayed reactions to system changes and hinder overall protocol governance or automation relying on these state transitions.
Fluffy Burlap Lark
Low/Info
No event emission while changing states from pausing to unpausing or vice-versa
Summary
The contract's
pause/unpausefunction does not emit an event when transitioning between paused and unpaused states. This can lead to difficulties in tracking and monitoring state changes, reducing transparency and making it harder for users and developers to detect when a critical function is temporarily disabled or re-enabled.Vulnerability Detail
In the code, the
pause_unpause.rsfile, found in theWOOFi_Solanaprogram, handles the pausing and unpausing of contract functionality. However, there is no event emitted when the contract's state transitions between paused and unpaused modes. This makes it difficult for off-chain tools and users to track these critical state changes efficiently.Impact
The absence of emitted events for pausing and unpausing operations can lead to reduced transparency, which affects the ability of users and off-chain services to monitor critical contract states effectively. This could result in delayed reactions to system changes and hinder overall protocol governance or automation relying on these state transitions.