Show Posts
I have been having problems with my bot as well, like you it's only been for the last few days.
If the site is down, there isn't a lot that can be done, so those don't bother me too much, but getting lots of these errors
HTTP/1.1 503 Service Temporarily Unavailable
and it appears to be happening mid script, so my guess is there has been a recent change to the frequency of API calls and they are now being rejected.
The docs do say that you should wait 3 seconds between each one (not sure if this is recently changed), which is what I have had to do to get it working again but it's not ideal.
Unfortunately with a bot there is no real way to avoid api calls, I only like to get a small percentage so I need to work out the speed available on both nicehash and westhash (2 calls). You need to scan all the orders to determine the current lowest price (2 calls), then you need to scan your orders to see what price you are currently paying (2 calls). This is before you even start to add/change/cancel/top up your orders
You don't need to scan all orders and then scan your orders, because your orders are already in all orders' response. You just need to filter all orders by your ordres' IDs. It's one call for "my orders", remember all IDs and then we have only "all orders" calls with filter. Let's unload API, let's make our algorithms better!If the site is down, there isn't a lot that can be done, so those don't bother me too much, but getting lots of these errors
HTTP/1.1 503 Service Temporarily Unavailable
and it appears to be happening mid script, so my guess is there has been a recent change to the frequency of API calls and they are now being rejected.
The docs do say that you should wait 3 seconds between each one (not sure if this is recently changed), which is what I have had to do to get it working again but it's not ideal.
Unfortunately with a bot there is no real way to avoid api calls, I only like to get a small percentage so I need to work out the speed available on both nicehash and westhash (2 calls). You need to scan all the orders to determine the current lowest price (2 calls), then you need to scan your orders to see what price you are currently paying (2 calls). This is before you even start to add/change/cancel/top up your orders
который будет умнее этих. И там не NicehashBot, боже упаси, он совсем тупой! Я, прежде чем написать своего, довольно продолжительное время наблюдал за рынком покупки мощностей. И так сказать мотал на ус. В итоге у меня в алгоритме есть параметр "здоровье", который отсекает моменты, когда маньячные заказы по невыгодным ценам забирают всю мощность пула и подтягивают все цены наверх (такое подозрение, что это делает сам Nicehash, чтобы уменьшить волатильность), есть параметр "острова", который ищут выгодное место среди заказов, чтобы и не в самом низу (тогда постоянно будет отрубать от майнеров при любом движении цен наверх), и не в невыгодной секции вверху, где непонятные люди майнят по завышенным ценам непонятно зачем. И много чего еще, включая API с бирж и сайтов с найденными блоками, чтобы корректировать цену и скорость.
