Description
The protocol supports pausing streams, but the pause_stream function does not emit an event. This makes it impossible for off-chain indexers and the frontend SDK to track the exact moment a stream was paused without polling the contract state.
Suggested Fix
- Define a new
StreamPaused event containing the stream_id, the caller address, and the timestamp.
- Emit this event at the end of the
pause_stream function execution.
- Ensure the
unpause_stream function also emits a corresponding StreamUnpaused event.
Description
The protocol supports pausing streams, but the
pause_streamfunction does not emit an event. This makes it impossible for off-chain indexers and the frontend SDK to track the exact moment a stream was paused without polling the contract state.Suggested Fix
StreamPausedevent containing thestream_id, thecalleraddress, and thetimestamp.pause_streamfunction execution.unpause_streamfunction also emits a correspondingStreamUnpausedevent.