[Passed] LiquidBits term 4 grant - Automatic Liquidity Pool (ALP)

Cybnate 2015-09-17 08:05:46 UTC #39

@tomjoad Just noticed that the liquidity page: https://nubits.com/liquidity-pools still shows that LiquidBits is supporting bitcoin.co.id, with this grant passing and since 15 September that is no longer the case. Could you please remove that reference? Thanks.

tomjoad 2015-09-18 00:33:39 UTC #40

Will do. Updating that page is on my list of priorities. I would like to divide the page into ALP’s and MLP’s, and simply link the ALP section to https://raw.nupool.net/nubits/. It doesn’t make much sense for me to continually manually update information that @willy and @woolly_sammoth are already tracking accurately. I may have time to complete this later this evening.

Cybnate 2015-09-26 23:46:12 UTC #41

Planned maintenance

Going to restart the server in next 5 minutes and load the new wrapper for Southexchange and also adding the Cryptsy for testing purposes.
Therefore there will be short outage (<10 minutes) in next hour or so assuming this goes well. Worst case I will roll back adding another up to another 10 minutes. Will also do a manual payout for the accumulated interest later today.

Cybnate 2015-09-27 00:22:35 UTC #42

Server is back up and running and testing of the Southexchange bot has started.

Apologies for the inconvenience.

Cybnate 2015-09-27 03:28:45 UTC #43

LiquidBits is down, the new exchanges are misbehaving and causing server.py to crash.
Investigating, most likely rolling back in next 10 minutes.

Cybnate 2015-09-27 03:52:46 UTC #44

Right, the Nu daemon also decided to not play nice:

    file unknown has LSN 4916/5242988, past end of log at 1/396444
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
__db_meta_setup: /home/cybnate/.nu/addr.dat: unexpected file type or format

Will have to rebuild the blockchain probably as I can’t think of anything else. Will see whether I can get server.py started while that is happening. This might result in no payout.

Edit: server is up but can’t submit liquidity until Nu Daemon has synchronised, this might take a few hours. You may chose to cancel your order as I can’t guarantee a payout over this period.

zoro 2015-09-27 05:30:07 UTC #45

of course i am not going to cancel any order! first priority: pegging

Cybnate 2015-09-27 05:51:39 UTC #46

Manual payout underway. This only covers the amount due before the server.py service crash.

The synchronisation with the growing blockchain is very slow and will take into my night before completed. When that is finished I possibly have to restart server.py in order to submit liquidity. If not, a normal payout will occur 24h after last restart which happened a few hours ago.

Again my apologies for this interruption of the LiquidBits service.

zoro 2015-09-27 06:08:33 UTC #47

have you pin point the problems? are due to the new exchanges or is like the previous server issues?
edit: i read more carefully, it is due to the new exchanges
have you seen proper behavior of cryptsy bot placing orders? in nuriver i cannot place any order!

Cybnate 2015-09-27 06:11:44 UTC #48

No, it was because of the new exchanges. There might have been a problem in the config file. I think I fixed it and I left Cryptsy out just to be sure. When it goes down again I will also roll back Southexchange testing.

Cybnate 2015-09-27 18:43:18 UTC #49

Another server.py crash. Rolled back to orignal. Nud database again corrupted. Started server.py, but not providing liquidity due to nud issues. Will look into this later today due to other commitments.

My sincere apologies.

zoro 2015-09-27 18:52:47 UTC #50

perhaps you should setup a new second server only for new exchanges in order to left intact the old ones

Cybnate 2015-09-28 08:23:41 UTC #51

Definitely a consideration, the cost and time have stopped me from doing that. But more important I shouldn’t try testing code myself and leave that to others

Cybnate 2015-09-28 09:21:51 UTC #52

Just restarted the server after getting the Nu daemon synchronised. The server should now be paying out automatically. Will wait until that has happened in about 24 hours from now. When successful I will dive into the logs to verify what backpay can be made based on the available logs. Given time constraints the backpay might take till the weekend as it requires a bit of work this time.

Thanks for your patience.

Cybnate 2015-09-29 09:36:52 UTC #53

Automatic payout for LiquidBits just occurred automatically and with that I expect the stability returns. As said will look into backpay over the weekend.

masterOfDisaster 2015-09-29 11:56:12 UTC #54

I can confirm that a payment arrived less than 2 hours ago.
The payment gap on 27th Sep and tiny payout on 28th Sep is due to the crashed server (and may lead to a manual payout if you have time to dig in the logs over the weekend)?

Cybnate 2015-09-30 08:00:43 UTC #55

Yes, that is correct. After that the server crashed another time and I had issues with the Nu daemon. So there will be a nice number of logs to work through for me. Can’t make it any better and my time is only limited.

masterOfDisaster 2015-09-30 08:03:52 UTC #56

Thanks for the feedback!

zoro 2015-09-30 08:06:04 UTC #57

perhaps you should consider to quit your daily job (or make it part time) and give NU the time it deserves
or is it too early for that?

Cybnate 2015-09-30 08:09:06 UTC #58

I would love to, but Nu can’t cover my basic cost of living yet. Will need to run another 10 ALPs concurrently