Queued withdrawals need slippage protection. Users enter the asset
amount they wish to withdraw, but they end up withdrawing a different amount. This final amount is set during the WithdrawalPool::_finalizeWithdrawals
function, which can get called at a much later time than the withdrawal initiation and the assets-shares
ratio has changed a lot.
Here is the point that the assets-share
ratio gets captured for the withdrawals of this batch
.
Users may withdraw
significantly less or more than they expected too, depending on the assets-share
ratio during the finalization of the withdrawal.
Manual review
Capture the assets-share
ratio at the time of the withdrawal
initiation or add slippage protection and return back the stLink
if the withdrawal falls outside the slippage.
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.