NuRiver Pool on Cryptsy for NBT/USD & NBT/BTC

[zoro]

no, please don’t try to “fix” your forked version, it is the only one that works for me

[masterOfDisaster]

Apparently it doesn’t work for cryptsy any longer which might be related to the wrapper being not properly included in it.
I was hoping for a release of all available bots in one place. And by “all available bots” I mean working versions of them.
I stop cluttering this thread and continue with posting results in Universal ALP bot collection - forked (and hopefully improved) @Nagalim edition :)

[masterOfDisaster]

One more post here, because it’s directly related to NuRiver on cryptsy.
I’ve tried https://github.com/inuitwallet/nu-pool/archive/1.22.zip

The error message when starting unix/client is

2015/09/24-08:53:35 ERROR: server missing in /tmp/tmp.5f7KEZIXoB

The end of the pool.conf is

server=45.55.43.33:3334
unit=btc
exchange=cryptsy

[woolly_sammoth]

apologies. This was raised by @Nagalim a few days ago (sorry for not replying to that too).
I had tried to reverse some of the logic in the client.py to avoid the large amount of nested ifs. I reverted it but neglected to revert the first reversed conditional which checks for the ‘server’ parameter.

I’ve fixed it and re-released. Apologies

inuitwallet/nu-pool

[masterOfDisaster]

I don’t know what’s wrong here. Am I overlooking something obvious?

I downloaded https://github.com/inuitwallet/nu-pool/archive/0.121.zip
I unzipped it.
I adjusted nu-pool-0.121/unix/pool.conf
I started ./client from nu-pool-0.121/unix/

This is the result:

nu-pool-0.121/unix $ ./client
2015/09/24-09:56:26 INFO: starting PyBot for btc on cryptsy
2015/09/24-09:56:29 INFO: successfully deleted all orders for btc on cryptsy
2015/09/24-09:56:29 INFO: waiting 0.20 seconds to synchronize with other trading bots for btc on cryptsy
2015/09/24-09:56:33 ERROR: unable to place bid btc order of "X" nbt at 0.00430516 on cryptsy: Insufficient BTC in account to complete this order.
^C2015/09/24-09:56:36 INFO: stopping trading bots, please allow the client up to 1 minute to terminate
2015/09/24-09:56:38 INFO: stopping PyBot for btc on cryptsy
2015/09/24-09:56:38 INFO: successfully deleted all orders for btc on cryptsy

[seki]

me too!
but someone has placed bid orders already!
Ask order target 0 NBT filled of maximum 1500 NBT ( 0% )
Bid order target 1225.54 NBT filled of maximum 1500 NBT ( 81.7% )

[masterOfDisaster]

I didn’t change anything, but recognized that the bot is placing orders again on the nuriver btc/nbt pair:

2015/09/24-15:28:36 INFO: price of btc moved from 0.00428807 to 0.00427917, will try to delete orders on cryptsy
2015/09/24-15:28:39 INFO: successfully deleted all orders for btc on cryptsy
2015/09/24-15:29:09 INFO: successfully placed bid btc order of "X" nbt at "Y" on cryptsy

[seki]

you lucky son of …
i am getting the same “no funds” error no matter what version i am using!

[masterOfDisaster]

That’s valuable information as we now know that it’s unlikely to be caused by a change of cryptsy’s API if it works for me again, but not for you!

ninjaedit: can you try to change the funds available for the bot?
Unfortunately it doesn’t have a limit for the bid side (only for the ask side). But you can put an insane (unlikely to be filled) order in another btc pair to “park” some of the funds.
That’s the only thing that changed at my bot: the available funds.
That’s why I’m recommending to try this…

[seki]

thanks, but didn’t work

[masterOfDisaster]

The error is back at my bot as well - and this time I haven’t done anything!

2015/09/24-15:59:31 INFO: starting PyBot for btc on cryptsy
2015/09/24-15:59:34 INFO: successfully deleted all orders for btc on cryptsy
2015/09/24-15:59:34 INFO: waiting 10.02 seconds to synchronize with other trading bots for btc on cryptsy
2015/09/24-15:59:48 ERROR: unable to place bid btc order of "X" nbt at 0.00425506 on cryptsy: Insufficient BTC in account to complete this order.

I don’t know what’s going on… Nothing changed, except for the BTC price (and something on cryptsy’s API?)

[nmei]

So…I’m going to need to shut down my server to update?

[Nagalim]

Restarting the server can be done with literally 5 seconds of downtime. Get everything prepared then run:

killall python
nuhop ./server.py &

Then you just need to do a manual payout using pay.py. However, I’m not sure there’s a fix for this cryptsy issue yet, so don’t go updating until we have a fix.

[woolly_sammoth]

As far as I can see the issue is only with the client. The server shouldn’t need to be updated.
The problem for me is that my tests placed the orders correctly. I’ll add more logging around the area of trouble and we’ll see what that reveals

[nmei]

@woolly_sammoth
Well the client is giving me the insufficient funds error again…
ERROR: unable to place bid usd order of XXXX nbt at 0.99500000 on cryptsy: Insufficient USD in account to complete this order.

That must be because Cryptsy dropped their trade fees in favor of transaction fees???

[zoro]

fortunately something that can be changed in ‘exchanges.py’ where fees and orders are set
i am not so good programmer to get it done

[masterOfDisaster]

There’s an adjustment of the cryptsy wrapper available for testing.
@woolly_sammoth has found a reason for the bad bot behaviour (not placing orders complaining about insufficient funds).
I’ve applied the changes to the latest experimental branch of the “Universal ALP bot collection”.
My first test indicate that the adjustment reliably solve the problem.

If you want to test yourself, you get it from here:

Lamz0rNewb/alp-collection

If you are not already familiar with the “Universal ALP bot collection” have a look here and make sure you know what you are doing:

Universal ALP bot collection - forked (and hopefully improved) @Nagalim edition

Disclaimer I won't take any responsibility for anything - not even that it still works. I'm a total github noob and don't know what I do. Run the stuff at your own risk! Getting down to the nitty-gritty: Preparing the start of NuRiver I thought it might please people (who want to run different ALP bots) to have a (hopefully) complete set of ALP bots. I leaned on the work of @Nagalim, who leaned on yada-yada-yada. I tried to fork @Nagalim's nu-pool, rework the unix folder section and adj…

Important sections are:

Disclaimer

I won’t take any responsibility for anything - not even that it still works.
I’m a total github noob and don’t know what I do.
Run the stuff at your own risk!
[…]
If you are looking for bots that are considered stable, because they have undergone sufficient testing, you need to look here:
https://github.com/Lamz0rNewb/alp-collection/tree/master

Not all exchanges/trading pairs are supported by this branch as it requires some testing before new wrappers/parameters are considered safe.
If you are interested in the latest versions, supporting more exchanges and more features, have a look at the experimental branches.
Keep in mind that the experimental branches bare that name for a reason!

[nmei]

Thanks! Testing it now…

[zoro]

orders are placed ok. But i have similar issue as in bter (nbt/cny). i have set both ask/bid orders
but sometimes only ask order is reported and be payed! I see also some socket errors (10060)

[masterOfDisaster]

I just want to confirm that the changes in the cryptsy wrapper by @woolly_sammoth solved the issue of bots not being able to place orders despite sufficient funds.
My bot runs almost flawless for more than 24 hours.
Flawless in this case means, there are still log messages like

2015/09/28-20:30:36 ERROR: unable to place bid btc order of "X" nbt at 0.00415489 on cryptsy: Insufficient BTC in account to complete this order.

but the bot automatically and reliably recovers from that inability.

Well done, @woolly_sammoth!