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

Liquidity Pools
#30

if i run the client.bat i get
ERROR: server missing in pool.conf
:frowning:

#31

Recommended settings for NBT/USD:

Recommended settings for NBT/BTC:

#32

Did you edit pool.conf?

At the end of the pool.conf there need to be either

  • NBT/USD server specifics
  • or NBT/BTC server specifics
#34

@Nagalim
Two different instances in two different folders on the server:
/server-usd
/server-btc

All with their own sub folders, configs, etc

#35

added to raw.nupool.net

#36

I hope you got the problem fixed.
If not, you might want to have a look here:

#37

thanks. it is a very strange error. it is like client.bat doesn’t recognize the server IP number :frowning:
if the whole “server” argument is missing from pool.conf, i get the ERROR: pool.conf could not be read: ‘server’.
i am reviewing the python program to see IF i can find the bug!

#38

Do you mind to try this?

Don’t forget to update the pool config file after you’ve downloaded and unzipped https://github.com/Lamz0rNewb/nu-pool/archive/experimental.zip! :wink:

1 Like
#39

this is working! thanks.
my very first bot experience :slight_smile:

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

By “that” you mean the bot from here: https://github.com/Lamz0rNewb/nu-pool/tree/experimental?

#41

exactly, the windows version

#42

Yeah!
I bet you started the bot directly and not using the “multiple ALP bot startup script” (alp-bot-sessions.bat), right?
You’re lucky that I decided to include a windows set of the bot collection :wink:

3 Likes
#43

yes directly. and i changed only the required parameters in the conf file.
the rest are unchanged.

#44

That’s how it should be.
This section needs attention:

### REQUIRED PARAMETERS ###

# NuBits payout address
address = xxxxxx

# API key from the exchange
apikey = xxxxxx

# API secret from the exchange
apisecret = xxxxxx

The rest can remain unchanged.

I tried my best to have all

### GENERAL OPERATION PARAMETERS - DO NOT CHANGE ###

server=
unit=
exchange=

settings correct as well as the recommended deviation and offset for each bot operation.
I wouldn’t guarantee that, though.

In fact most of the settings are still like they had been in @Nagalim’s version. I adjusted some of them settings based on his recent recommendations.

The pool settings in the unix and windows section should be identical.

In case you find something that doesn’t match, feel free to tell me in the “Universal ALP bot collection - forked (and hopefully improved) @Nagalim edition"” thread or make a pull request in github :wink:

1 Like
#45

payouts are working daily at a fixed time?
and the amount the bot reports as “balance” is accurate?

#46

Payouts occur at ~ 1700 EST. Yes the balance is accurate.
You must have greater than 1 NBT to have a payout.

2 Likes
#47

I suppose your bot is running fine.
If you want to extend your liquidity operation to other exchanges (or shift a part of it) this is very conveniently possible with your awesome bot collection!
…not trying to move liquidity providers away from NuRiver - I’m very glad to see another ALP! - but spreading money across exchanges equals balancing exchange default risk; just sayin’…

#48

waiting for my first payment from the pool, i just check cryptsy and i see that i have zero balance of NBT and BTC after the bot cancelled the orders!
i sent them a support message to check it, i didn’t have any hacking or withdrawing!
lets hope they solve it soon!

they answered already!
"We are performing some routine maintenance on the site. Your balances may be slow to adjust properly however your funds are safe and balances will be corrected shortly after the maintenance is over. "
:smiley:

#49

I just want to confirm that I’ve received 2 payouts so far!

Some statistics of my bot:
my logs contain 3,913 lines reporting status including efficiency.

  • 3,890 have “rejects: 0 missings: 0”
  • 3,722 have “efficiency: 100.00%”

Digging deeper in the logs showed 170 lines like this:

2015/09/10-04:51:09 INFO: cryptsy - balance: 0.00000000 rate: 0.00% ppm: 0.00000000 efficiency: 0.00% rejects: 0 missings: 0

I think there was something wrong with my connection that caused “efficiency: 0.00% rejects: 0 missings: 0”.
I’m removing these 170 lines from the calculation, adjusting the numbers to:

  • 3,743 accounted for report lines
  • 3,722 have “efficiency: 100.00%”

I give NuRiver on cryptsy 99.47% (3,722 of 3,743) reliability.

That’s impressive!

…and I have some other ALP bots to compare with :wink:

1 Like
#50

those lines with zero balance is exactly the same logs i saw due to the cryptsy maintenance issue :wink:
not a bot problem :wink: