added a 'localAddress' option to specify which IP is to be used for r…

[DoobleD]

I added a 'localAddress' option to specify which IP is to be used for requests to Binance API (allows the use of multi IP on a single server).

Usage :

const binance = require('node-binance-api')().options({
  localAddress: '94.23.25.209',
  APIKEY: '<key>',
  APISECRET: '<secret>',
  useServerTime: true // If you get timestamp errors, synchronize to server time at startup
});

All requests will then use the IP given by localAddress ('94.23.25.209' in the example above). You can then run say 10 bots on a single server, with 10 different IPs.

Why do that? Because Binance has API usage limits for IPs. Use several IPs thus allows to trade more, or to run different strategies and bots simultaneously with each one having the full usage limits for its IP. See https://www.binance.com/en/support/articles/360004492232

Of course you need to own the IPs you specify in the 'localAddress' parameter and have them configured on your server.

Works well on my server.

[TravisBuddy]

Hey @DoobleD,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: 8f756530-d3ce-11e9-9a2a-b93990a2c4d9

[jaggedsoft]

Thank you very much for your contribution, friend. Are you aware if this works on ipv6 addresses?

[DoobleD]

My pleasure! Good question. I see you've already hit it 4 years ago <request/request#1944>. Following the hashtags, it seems a fix has been merged <nodejs/node#6654> since then for the 'family: 6' option, which allows for ipv6 addresses. We coud check whether the 'localAddress' provided is ipv4 or ipv6 (with this <https://github.com/keverw/range_check> for instance), and in case of ipv6, add the 'family: 6' option? I have no ipv6 at my disposal to test it though. Feel free to try if you're motivated, or disregard the PR otherwise. :)

…

On Tue, 10 Sep 2019 at 15:29, Jon Eyrick ***@***.***> wrote: Thank you very much for your contribution, friend. Are you aware if this works on ipv6 addresses? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#356>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHAFOJMLOYFHLUTRMJDW7DQI6OLNANCNFSM4IVHQSGQ> .

-- Pierre Allétru 06 70 55 08 35 [email protected]

[DoobleD]

Also I realize the line localAddress: Binance.options.localAddress should probably also be added in reqObjPost, between lines 138 and 139.

It seems I was using an older version of node-binance-api (0.8.5) which didn't have that reqObjPost variable.

[jaggedsoft]

Forgot about this until now, very sorry but I appreciate your hard work!
8feb271

for promiseRequest it might be easier to switch to umi-request otherwise we have to define a custom Agent

[jaggedsoft]

better late than never I guess 😏 finally got to take advantage of the issue I filed 4 years ago
cheers

[w4l73r]

Hi
In order to allow this option to be used everywhere (especially on the futures api), you need to add localAddress: Binance.options.localAddress, to the promiseRequest function (line 540)
Can you please provide a patch ?

[mhdmirel]

this does not work. How do I run

const binance = require('node-binance-api')().options({
  localAddress: '94.23.25.209',
  APIKEY: '<key>',
  APISECRET: '<secret>',
  useServerTime: true // If you get timestamp errors, synchronize to server time at startup
});