About two hours ago I started to recognize a problem with Bittrex. The server only barely gets requests validated and I think some of you will have an efficiency of around 0 now. Sometimes it recovers for a while, but all data during those (long) periods is faulty. When talking to Bittrex they already warned me that Cloudfare might throttle the server, but I cannot say if this is in any way related to our current problem.
What I did now is to modify the Bittrex client in the way that it ensures that only one order per market side will be placed at a time. This means previous orders will simply be removed before placing a new one. This will reduce the number of calls to the exchange and hopefully solve our problem for now:
https://github.com/creon-nu/nu-pool/releases/tag/0.9
THIS UPDATE IS MANDATORY!
We will update the server once @woolly_sammoth and @willy are awake. When we did this, the server will not accept more than two orders (buy/sell) in a request of a user, such that requests from old client in some cases will get rejected. So please update the client as soon as possible to reduce the load on the current server.
I can only hope that it will improve the situation. Furthermore I am eagerly trying to get in contact with Bittrex to get more information from their side. Don’t know what else to say than sorry - with 10 users and more than 7000 NBT liquidity on day one the operation already scaled to a multiple of the beta and these problems were hardly observable from my tests.
Important: When the server restarts, all balances will be reset to zero. I will personally take care that all open balances will be sent (manually) when we restart the server. Furthermore be assured that your funds are not at risk, also not on the current server. The trading bot is not affected by all this, its only the server <-> exchange communication which creates this problem.
Thank you for your understanding!