The recipient
can have an onLockupStreamWithdrawn
function to be notified of withdrawals
.
This function may contain important logic
that needs to be executed based on the new withdrawals
.
Currently, we do not invoke this callback
function when the msg.sender
is the recipient
.
However, the recipient
still wants the consequent logic
in the callback
function to be executed when they withdraw funds
.
Right now, the recipient
must perform a second transaction to execute this logic, which is inefficient.
Therefore, we should modify the system to always invoke the onLockupStreamWithdrawn
function when a withdrawal
occurs, whether the msg.sender
is the recipient
or the sender
of the stream
.
This change ensures that the necessary logic is executed in all cases without requiring additional transactions.
Manual
https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity
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.