-
Notifications
You must be signed in to change notification settings - Fork 41
Claimable Withdraw should be upper bounded by available balance #339
Comments
I though we did that, but apparently not. Thanks for reporting it. I agree this is a better ux. |
I believe I used etherscan to request my withdraw. If the UI in itself doesn’t allow for this consider it low pri. However, how does one request an optimistic withdraw “in advance” if it’s capped at the currently available balance? |
Good question, we don't allow "optimistic withdraw" as we defined the user workflow for the user Do you think we should allow it for this version? Not sure if it makes that part sense for now. |
Since the UI itself does not allow this behaviour, is there still something to be done? I'll close this issue for now. Feel free to re-open if there's any action to be taken. |
Note, that this issue is very related to gnosis/dex-contracts#539 The smart contract itself doesn't allow you to read the available balance but in js you could read contract storage at the right address in order to fetch it. |
If I create a withdraw request for a large amount, it will show that amount in the UI even though my available balance in the exchange wallet might be much smaller.
Would it make sense to "upper bound" the amount displayed by the amount available in the exchange?
The text was updated successfully, but these errors were encountered: