Precision Bug about jesse HOT 3 CLOSED

That is how I did it at first too. But later we had errors related to price precision. After digging I found out that the pricePrecision is not the correct precision that Binance expects. Instead the tickSize from the filters section of that endpoint is. We had no errors after that. Here's my code:

'price_precision': int(
    abs(math.log10(float(si['filters'][0]['tickSize'])))
),
'qty_precision': int(si['quantityPrecision']),

from jesse.

can you check if jesse take the QUARTER "pricePrecision" as the PERPETUAL ...?

what I mean is,

maybe, there will be an error, even it use tickSize to caculate price_precision

If jesse use the "pair": "BTCUSDT", not the "symbol": "BTCUSDT" (data from binance exchangeInfo) as the BTCUSDT pricePrecision

cos the QUARTER and PERPETUAL with the same "pair", but not the same "symbol"....

from jesse.

It always uses PERPETUAL data as only they are supported by Jesse

from jesse.