NuPool 2 now active on Bittrex and Poloniex

Good Morning Shareholders.

The new operation of NuPool is now live on Bittrex and Poloniex. The updated server has run successfully overnight with a few users and not reported any issues.

It is recommended that you use the newest client to operate on NuPool. This can be found here https://github.com/inuitwallet/nu-pool
The biggest change to the client is the addition of a pool.conf.json file and a new python script called run_client.py. This is provided to allow a quick way to run clients on both Bittrex and Poloniex simultaneously.

The pool.config.json file looks like this:

[ { "server" : "eu.nupool.net", "exchange": "bittrex", "unit": "btc", "address": "xxx", "api_key": "xxx", "api_secret": "xxx", "bid_interest": 0.001, "ask_interest": 0.001, "bot": "pybot", "order_match": true }, { "server" : "eu.nupool.net", "exchange": "poloniex", "unit": "btc", "address": "xxx", "api_key": "xxx", "api_secret": "xxx", "bid_interest": 0.001, "ask_interest": 0.001, "bot": "pybot", "order_match": true } ]

simply fill in your payout address and api key and secret to the appropriate sections and then run the run_client.py script. This will start a client on both Bittrex and Poloniex using the supplied values.
If you only want to run a client on one or other exchange, you can use the existing pool.conf method found in the unix or windows folders of nu-pool.

It is also worth mentioning that the order_match parameter now defaults to True if not specified. This setting will instruct your client to place bid or ask orders even if it will clash with an existing opposite order on the exchange. In practise this means that your client will buy NBT that are available at 5% cheaper than the determined $1 value or sell them to bid orders that are 5% higher. It will also prevent the liquidity from getting ā€˜stuckā€™ when such orders exist.

A quick reminder of the Pool targets and payouts:

  • Targets of 17,500 NBT on each side of each exchange (35k per exchange, 70k in total)
  • Max daily rate of 0.3% or 9% per month

As stated in the grant proposal, the main aim of this run will be to attract users from outside of Nu to provide liquidity or become pool operators. Work has already started on a website https://nupool.net/ and community outreach will begin in earnest tomorrow.

Thank you again for voting for this grant.

6 Likes

Updated client: check (git clone https://github.com/inuitwallet/nu-pool.git)
Moved NBT to bittrex: check
Updated pool.conf.json: check (but only the bittrex part; do I need to remove the poloniex part or can it simply not be used due to invalid setting?)
Started run_client.py: errors

./run_client.py: Line 1: import: Command not found.
from: can't read /var/mail/python
./run_client.py: Line 3: import: Command not found.
./run_client.py: Line 5: __author__: Command not found.
./run_client.py: Line 7: Syntax error at unexpected word `('
./run_client.py: Line 7: `config = json.load(open('pool.conf.json'))

Updated unix/pool.conf instead and started client.py.
That runs fine.

try running it with ā€œpython run_client.pyā€

Thank you, thatā€™s working!
Iā€™ve removed the poloniex data set from the pool.conf.json in addition.
Watching it closely :wink:

edit: still running like a charm at bittrex thanks to @woolly_sammoth, @willy and @creon (who isnā€™t part of nupool 2, but who paved the ground by creating TLLP!)

Thanks @masterOfDisaster. Glad it is/was running well for you.

I just had to restart the server. Iā€™m a dingus and managed to set the Target Liquidity for each side as the total liquidity for each exchange! I really shouldnā€™t be allowed near a computer before iā€™ve had my coffee.
The server is back up and running now and all outstanding balances have been paid. Apologies for any inconvenience

That explains the error messages that started with (time UTC)

2015/05/17-20:44:25 ERROR: submit: server response invalid

but after the bot automatically deleted the orders (2 minutes later it lost connection to the server - just like it should be)

2015/05/17-20:46:27 INFO: stopping PyBot for btc on bittrex
2015/05/17-20:46:29 INFO: successfully deleted all orders for btc on bittrex

the server obviously went up again an the bot resumed activity

2015/05/17-20:47:02 INFO: successfully placed ask btc order of 200.0000 nbt at 0.00424663 on bittrex

I could have spared you from basically writing nothing but ā€œeverythingā€™s fine hereā€, but I think positive feedback about the robustness of the botā€™s activity is welcome as well as negative feedback as it helps verifying the proper function of the bot!

2 Likes

Sometimes the bid/ask amount would be heavily reduced, even though there is space for liquidity on both sides. Some other times there would be open orders left on the exchange for long periods of time but not counted towards the interest. The problem would be solved after a restart, so itā€™s not by design.

Can you send us your log file to support@nupool.net ?

Part of the grant proposal for NuPool 2 was to engage in community outreach to attract liquidity providers external to Nu.
Iā€™m pleased to say that the first bitcointalk post has gone up
https://bitcointalk.org/index.php?topic=1065799.new#new

If anyone feels like commenting, please feel free.

Posts will follow on Peercointalk, Reddit and others.
Ninja Edit: https://www.peercointalk.org/index.php?topic=4133.new#new
Ninja Edit 2: http://www.reddit.com/r/CryptoCurrency/comments/36jri7/earn_compensation_providing_liquidity_for_nubits/

Also worth mentioning that the NuPool website is active on http://nupool.net

5 Likes

well done.

1 Like

@woolly_sammoth, in your post you said gamifaction, when I think you meant to say gamification.

Edit: Also posted a message on all the threads. Everyone should post a comment as well. We need it to help generate awareness of these pools.

1 Like

Thanks for that spot. Iā€™ve edited the post accordingly.

Sometimes the bid/ask amount would be heavily reduced, even though there is space for liquidity on both sides. Some other times there would be open orders left on the exchange for long periods of time but not counted towards the interest. The problem would be solved after a restart, so itā€™s not by design

Apologies for the delay in replying to this.
The loosing of orders is something that is being reported on Cybnates liquidbits pool too. Are you experiencing the same on NuPool?
As willy says, a copy of your log file (/nu-pool/python/logs/*) would be a great help.

Another post. Hope to get some BTC interest

working fine here.

@woolly_sammoth, you have some questions in the bitcointalk thread.

Thanks. Iā€™ll answer them when Iā€™m at a proper keyboard.

Thanks for the replies, I want to anonymize the logs before I send them in, and Iā€™ll do it when I have more time. Meanwhile, I noticed the problems donā€™t seem to happen with BTC/NBT asks.

get these error :sweat:

@woolly_sammoth

2015/05/27-14:24:30 DEBUG: starting liquidity operation with sampling 48
2015/05/27-14:24:30 INFO: starting PyBot for btc on poloniex
2015/05/27-14:24:31 ERROR: unable to delete all orders for btc on poloniex: exception caught: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
2015/05/27-14:24:31 INFO: adjusting nonce of poloniex to 101
2015/05/27-14:24:32 ERROR: unable to delete all orders for btc on poloniex: exception caught: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
2015/05/27-14:24:32 INFO: adjusting nonce of poloniex to 201
2015/05/27-14:24:32 ERROR: unable to delete all orders for btc on poloniex: exception caught: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
2015/05/27-14:24:32 INFO: adjusting nonce of poloniex to 301

Poloniex has announced downtime today. Does this error still persist?

https://twitter.com/Poloniex/status/603256867704283138