Get RANDOM api key and secret in GunBot (+3.3)

[leeview]

// * 1. GENERATE API KEYS IN POLONIEX
// * 2. GIVE GUNTHAR THE NEW API KEYS (public key / not secret key)
// * 3. ADD THE FOLLOWING LINES TO ALLPAIRS-params.js

/////////////////////////////////////////////////////////////////////////////////////////////////////////

// *** IN THE TOP of ALLPAIRS-params.js
var randrreturn = ['api1', 'api2', 'api3', 'api4','api5'][Math.floor(Math.random() * 5)]
var objapilist = {
    'api1' : {
        'api' : 'API-KEY-1',
        'secret' : 'API-SECRET-GOES-HERE'
    },
    'api2' : {
        'api' : 'API-KEY-2',
        'secret' : 'API-SECRET-GOES-HERE'
    },
    'api3' : {
        'api' : 'API-KEY-3',
        'secret' : 'API-SECRET-GOES-HERE'
    },
    'api4' : {
        'api' : 'API-KEY-4',
        'secret' : 'API-SECRET-GOES-HERE'
    },
    'api5' : {
        'api' : 'API-KEY-5',
        'secret' : 'API-SECRET-GOES-HERE'
    }
};
/////////////////////////////////////////////////////////////////////////////////////////////////////////

// *** IN THE var config = { ADD the following lines

    //---POLONIEX RANDOM API key and secret
    POLONIEX_KEY: objapilist[randrreturn]["api"],
    POLONIEX_SECRET: objapilist[randrreturn]["secret"],

[BitFlipp4r]

Is this to fix 422 Errors? How many are we supposed to make for lets say 15 pairs?

[leeview]

people said that having multiple api keys can reduce the 422/429 erros that come from Polo ..

From my experience this is FALSE as it is all related to the IP and requests per IP .. but to let people test it out, i wrote that code for Random Api Keys.

[CoinKombinat]

I am testing it atm, causes IP nor API the trouble. For connections > 7/sec = no doubt, dont do it 

@liviuv : did u tested same API Key with different IP's?

BTW i am testing socks proxies but results are not clear yet.

[BitFlipp4r]

Well I did fix a 422-loop with a lending bot once by using a new api key.
So I will try this.

[BitFlipp4r]

I definitely get less 422 errors using multiple keys.
Now using 6 keys for 18 pairs. 280s delay. 220s error delay.

[leeview]

I am testing it atm, causes IP nor API the trouble. For connections > 7/sec = no doubt, dont do it 

@liviuv : did u tested same API Key with different IP's?

BTW i am testing socks proxies but results are not clear yet.

I did try to use a VPN with USA IP's, on my windows VPS ... but nothing seems to change sadly ..

[cryptopesa]

What is the logic of this random API?

1. once a pair has been locked into a certain API does it lock-in indefinitely?
2. does it try a new one if current fails?
3. does it try to equally distribute to all keys?

Thanks.

[allanster]

They are rolling keys. See link I posted here... https://gunthy.org/index.php?topic=551.0, it is Coinigy's blog explaining and they seem to think it does help.