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 adjust
python/client.py (include cryptsy wrapper) python/server.py (include cryptsy wrapper) python/exchange.py (include cryptsy wrapper)
Have a look at the commits if you are interested in the details of the changes
I haven’t changed the Windows section. On demand I’ll do that as well.
I admit that I had running ALPs on a RaspberryPi in mind when I did this (I recommend running the ALPs in
screen sessions - maybe I work on a script to generate them automatically if I find the time…)
I haven’t changed any of @Nagalim’s pool parameters after forking the repo.
I leaned on @Nagalim’s suggestion for the pool settings of NuRiver’s USD pair and tried to derive the settings for the BTC pair from it followed his recommendation for the BTC pair as well.
The reason for creating a dedicated folder for each exchange and trade pair was to make it easier run 2 (or more) ALP bots on the same exchange - otherwise you’ll get a mess with the logs.
Piece of advice: make different exchange accounts if you want to run different bots on the same exchange - otherwise they’ll fight for your balance.
Another piece of advice if you use different NBT addresses for each ALP bot, you can easily track your compensation!
Have a go at it, if you are fearless: https://github.com/Lamz0rNewb/nu-pool
The repo name changed. It can now be found at: https://github.com/Lamz0rNewb/alp-collection/
And it got an experimental branch with some scripts in the unix section and support for the test run of a fixed rate ALP: https://github.com/Lamz0rNewb/alp-collection/tree/experimental/unix
Remark: NuRiver on cryptsy with trade pair NBT/BTC doesn’t have a complete pool config (server data is missing), because @nmei is still busy with setting up the server for that.
NuRiver on cryptsy with trade pair NBT/BTC pool config complete.
If you are looking for bots that are considered stable, because they have undergone sufficient testing, you need to look here:
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
Keep in mind that the
experimental branches bare that name for a reason!
- “restime” in the pool config is now called “reset_timer” and by default on 0.5 hours
- southxchange bots for windows and unix on liquidbits.net have been prepared (but are missing server conf as well as proper offset and deviation settings)
- pool config contains a new option to limit the amount of NBT that is put into tier1 (=on the order book):
# Maximum NBT to place on sell side fillfactor = 10000
- cryptsy wrapper adjusted to make it compatible with the current fee structrure.
- adjusted bot, because fixed cost test run on bter isn’t on cny but btc pair
Older bot versions might show this error:
ERROR: unable to place bid btc order of "X" nbt at "Y" on cryptsy: Insufficient BTC in account to complete this order
although there are enough funds to place the order.
1. Cryptsy wrapper
There’s some trouble with the NuRiver BTC bot that creates error messages like
unable to place bid btc order of "X" nbt at "Y" on cryptsy: Insufficient BTC in account to complete this order.
Repo will be updates as soon as a fix is available.
Fix has been applied and is available for testing.
As I don’t know what caused the trouble and what resolved it, this stays for the time being in the known issues section.
It looks like the trouble was related to the changes in cryptsy’s fee model.
The issue remains tracked until it’s verified that the latest change of the wrapper solves the problem and the change has been merged with the master branch.
An update was pushed to the cryptsy wrapper following the latest changes in https://github.com/inuitwallet/nu-pool/blob/extra-cryptsy-logging/python/exchanges.py#L330.
Only https://github.com/Lamz0rNewb/alp-collection/tree/experimental-0.51 contains this adjustment until further tests have shown that it’s safe to apply it to the other branches as well.
- removed nupond_bter_btc_fix_payout_test because nupond_bter_btc is now fixed cost
- added southx usd trading bot