I’m aware that this already creates a lot of efforts, but…
…could this be an opportunity to make a hard cut over to ALPv2?
I mean, the ALP clients need to upgrade, because of the changed CCEDK API, right?
A properly scheduled and announced change would be way better.
But it seems that it’s already too late for that.
It has me puzzled too. The server has been down for 12h now. They haven’t been cancelled clearly. Doing another attempt to revive the server before I have to attend to other commitments for most of the day.
It is not that it is ready to fly, had planned to look into it over Easter. It will need to be tested and understood before it runs safely and secure. I’m not a developer and not a full-time system administrator. It will take time.
Edit: it is unclear what is going on, just did a full restore from a backup one week old. I’m unable to start the server.py successfully for CCEDK or Bittrex/Poloniex. The PID runs but there is no logging output and its bots can’t see it. This is really weird. I’m running out of options. Will make another attempt tonight with an even older backup.
I can’t make it work on windows 7.
I am getting the error: unable to receive balance for nbt on ccedk.
I have removed old python installation 2.7.9, perform a restart and install the new python 2.7.11
Has anyone succeeded?
I asked CCEDK to remove the ‘-’ between the US and NBT as someone else asked coinmarketcap.com (CMC) to use the USNBT denomination instead. I hoped that this change would make CMC recognise CCEDK and the BKS market again. This doesn’t appear to be the case though. I’m intending to contact CMC about this unless someone PMs or asks me in this thread not to or is already taking care of this.
Re API; I asked CCEDK to not touch the API or inform us if required. The change can be made reasonably quickly if needed, but I haven’t encountered any problems yet even after a restart of Pybot where that was the case with the previous change. Please let me know if you encounter problems and I will test and make the change asap.
my client as been stuck in the beginning with no output. When pressing ctrl-c it says the config file couldn;t be read, an error that happened before and was found associated with reading ccedk time-out.
A while ago the NuRPC and the server.py became detached for an yet unknown reason. Therefore the by LiquidBits provided liquidity is no longer (correctly) broadcast on the network but still available on the exchanges. The only way to fix the broadcast is to restart the server.py and Nu. I will do that after the next payout around 7.40am UTC to minimize the impact on the payouts.
There are still issues with the LiquidBits server. I’m unable to place orders on Poloniex and Bittrex although the PyBots believe all is fine. Orders on CCEDK are fine, but the automatic payout didn’t come through. Apparently there are some Cloudflare issues affecting this and other operations. I’m sitting it out until it is clear what is going on before reverting back to a backup tomorrow if it doesn’t resolve itself.