Futures ETHUSDT market has an issue in JSON.parse

[wwforever]

Futures ETHUSDT market has an issue in JSON.parse (I don't know if it occurs in Spot or Coin-m, etc.)

The order id value of Ethereum has been changed from Number to Bigint.
It seems to have occurred around December 9, 2020. It is believed that the issue occurred after Binance supported Ethereum 2.0 staking.

I solved it using JSON-bigint.
https://github.com/sidorares/json-bigint

Change JSON.parse to JSONbig.parse in line 182 reqHandler function.
Change JSON.parse to JSONbig.parse.In line 509 promiseRequest function.

[jaggedsoft]

Thank you very much!
40f3da3

[kalinbas]

This should be changed anywhere (e.g. also in WS Streams). Another issue here is that when I have a BigNumber OrderId and want to call CancelOrder with it, can i be sure it is serialized in the correct way?

[jaggedsoft]

these were all strings in the past if i remember correctly

[Kuzmich100kM]

Help me plz.
At futures ETHUSDT market function order_update_callback return orderId like here

But the real orderId is

[c0sm1cdus7]

@jaggedsoft

Did you manage to fix this?

[doppelgunner]

@jaggedsoft please fix this

[doppelgunner]

I already made PR for this @jaggedsoft

Please merge:
#890

[doppelgunner]

In themeantime i created node-binance-api-2 so that you can use this while the PR #890 is not merged:

• https://www.npmjs.com/package/node-binance-api-2