New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitstamp bug: miscalculates % distance from market price #823
Comments
Ok I figured this out. The error message made things as clear as mud. It would have been nice if it had said the percentage over the market price in that error message. I thought "distance in % from market price" was "percent of market price" - i wanted to list something 99% of market price (1% distance). Better error message or titling is needed here |
This wording also got me tripped at first. Maybe a display of a quick calc of what the price could be at the time of placing a bid or ask could help. Indicative. EDIT: More visually, I'd display an estimated price, in grey, to the right of the percentage sign in the screenshot above. |
Thanks for the input. As soon we have a dedicated UI dev we will re-work that screen. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
I really question the value of closing stale tickets. Does this bug still exist? Why close this ticket if the bug persists? |
@fresheneesz That is actually what this auto-stale is all about. Issues with labels like |
I'm trying to do this trade:
It says its 99.02% from market price, which seems correct to me. However, when I press next step, it pops up a blocking warning that says "The price you have entered is outside the max. allowed deviation from the market price. The max allowed deviation is 10.00%..."
So.. 99.02% seems like less than 1% off market price - clearly not over 10%. So what's going on here?
The text was updated successfully, but these errors were encountered: