This repository has been archived by the owner on Nov 26, 2022. It is now read-only.
Binance gives the wrong price for executed order #151
Labels
Comments
This was referenced Jan 11, 2018
So, this was answered in the attached CCXT issue. Binance (and a handful of other exchanges) don't put the trade execution data in the filled order objects. We need to use the |
fredfortier
added a commit
that referenced
this issue
Jan 12, 2018
…rocessing order for exchanges supporting "fetch-my-trades"
fredfortier
added a commit
that referenced
this issue
Jan 12, 2018
…rocessing order for exchanges supporting "fetch-my-trades"
Currently testing in live trading before releasing. |
Is binance available on catalyst ? It seems that the ingest function does not work for it. |
Only in live and paper trading modes.
…On Tue, Jan 16, 2018 at 7:10 AM Ming Yu Lu ***@***.***> wrote:
Is binance available on catalyst ? It seems that the ingest function does
not work for it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#151 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZ-Qt3qL1tPMK4i51agOAk47hUfqX-oks5tLLvegaJpZM4RaR-h>
.
|
Fixed on 0.4.6 please re-open if you still notice an issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In relation to issue #150 , I noticed that binance gives the wrong price for an executed order. Based on this screenshot, I'd expect Binance to respond to the "Avg" price of the order (0.00000827). Instead, it responds with the limit price of the order. This explains why we don't get a price for market orders.
Here is the order object (0.00000827 not in the payload):
We may fix this on the CCXT side after further investigation.
The text was updated successfully, but these errors were encountered: