-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Potential something-for-nothing fill bug #184
Comments
From @theoreticalbts on February 29, 2016 15:35 order_id in question is 1.7.104874 |
From @svk31 on March 8, 2016 8:22 We're getting a lot of these at the moment, would be great if this could get looked at sooner rather than later. As you can see from the below screenshot it causes the price to go to 0, and in the inverse market direction the charts fail due to Inf values.. |
This just happened again in the BTS:USD market. Full json of the order history object:
There's a logic in the witness_node called maybe_cull_small_orders, it seems to me that should've taken care of this order and cancelled it, but for some reason that's not working correctly. |
…after hardfork555.
As of writing, this issue has occurred 23524 times, and the number is still counting. Will address it in #641. |
Done with #830. Closing. |
From @theoreticalbts on February 29, 2016 15:31
This report from @svk31 on Slack:
something strange appears to have happened in the BTS:METAEX.BTC market: an order appears to have happened where someone paid 0 METAEX.BTC and received 1 satoshi BTS, making the price go to infinity or zero depending on your market direction
it's causing issues in the GUI when looking at that market
Possible duplicate of cryptonomex/graphene#555
Copied from original issue: cryptonomex/graphene#601
The text was updated successfully, but these errors were encountered: