For whatever reason a user might want to see a depletion time of a stream, they should be able to, by calling the depletionTimeOf(streamId)
, however, this function can be bricked by pausing which is controlled by sender and can be done for malicious reasons.
a user calls the depletion time of to become informed about whether contributing to a stream might be a good idea or good timing, this function can be disabled by a sender simply pausing the stream causing the function to revert.
`user calls -> depletionTimeOf -> sender frontruns pausing the flow stream before the call is executed`
users will not be able to use the depletionTime function for as long as the sender
decides.
Manual review
depletion time should be calculated in a way that accomodates 0 flow stream rates and does not revert as a view function
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.