You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
Consider making the price estimation more tight (don't subtract any value on top of the fees), and then offer these options:
0.5% would be the default option and pre-selected, so the price inputs it's already auto-filled with this value.
@koeppelmann, this percentages goes on top of the fees, right? because the actual price - 0.2% is the price that would make a solution feasible, so that would be the price at 0% (which we don't offer)
Let's see the proposal with an example:
An user wants to change 100 DAI for USDC
There's an order of 100 USDC for 100 DAI in the order book
The price estimation will return 99.8
The UI will offer:
0.1% = 99.7002
0.5% (default) = 99.301
1% = 98.802
For the custom field, 0% would be a valid value, but also negative amounts, that would give you a better price, but the order won't probably be fulfilled soon.
Consider making the price estimation more tight (don't subtract any value on top of the fees), and then offer these options:
0.5%
would be the default option and pre-selected, so the price inputs it's already auto-filled with this value.@koeppelmann, this percentages goes on top of the fees, right? because the
actual price - 0.2%
is the price that would make a solution feasible, so that would be the price at0%
(which we don't offer)Let's see the proposal with an example:
100 DAI for USDC
100 USDC for 100 DAI
in the order book99.8
The UI will offer:
For the custom field, 0% would be a valid value, but also negative amounts, that would give you a better price, but the order won't probably be fulfilled soon.
cc/ @fleupold @alfetopito @c3rnst
The text was updated successfully, but these errors were encountered: