[Passed] NuPool 8 ALPv2

[nmei]

Call this a feature request…
When we call up the JSON on eu.nupool - could we get the server price quoted in NBT/BTC and BTC/NBT.

[huafei]

{“message”: {“meta”: {“last-credit-time”: 1461548927, “next-payout-time”: 1461570221, “number-of-orders”: 10, “number-of-users”: 16, “number-of-users-active”: 6}, “prices”: {“btc”: 454.94}, “rewards”: {“bittrex”: {“btc”: {“ask”: {“rank_1”: 0.00128506, “rank_2”: 0.0}, “bid”: {“rank_1”: 0.00128506, “rank_2”: 0.0}}}, “poloniex”: {“btc”: {“ask”: {“rank_1”: 0.012155, “rank_2”: 0.0}, “bid”: {“rank_1”: 0.012155, “rank_2”: 0.0}}}}, “totals”: {“bittrex”: {“btc”: {“ask”: {“rank_1”: 1586.00421423, “rank_2”: 0.0, “total”: 1586.00421423}, “bid”: {“rank_1”: 0.0, “rank_2”: 0.0, “total”: 0.0}, “total”: 1586.00421423}}, “poloniex”: {“btc”: {“ask”: {“rank_1”: 15563.39723982, “rank_2”: 0.0, “total”: 15563.39723982}, “bid”: {“rank_1”: 0.0, “rank_2”: 102.94036956, “total”: 102.94036956}, “total”: 15666.337609380002}}}}, “server_time”: 1461548952, “server_up_time”: 69087, “status”: true}

price of ALP is 454 , while the price of market is 460…

[woolly_sammoth]

Yeah, it looks like that price parameter is still not updating correctly. I will take another look when I do more work on an updated price feed model.
I’m happy that the stuck price shown isn’t affecting the way the pool credits orders. Checking the database, there are differences in the pool price shown indicating that different prices are used when they exist. Also we’d commonly see all orders in rank_2 much more often if the price was truly stuck.
For your own orders you can check https://eu.nupool.net/<api_key>/orders which will show you the price used to calculate your rabk

[zoro]

I see that i have been double payed, again!
There is something wrong with payment system.
Please give me a nbt address to sent back the extra payment

[woolly_sammoth]

So looks like my restart of the server this morning coincided with the payout which was underway. The routine to mark credits as paid hadn’t completed.

You said that you were double paid again. HOw many times have you noticed this? I looked through the logs and this is the only instance I can see.

As this was my fault, I’m happy to absorb the cost of this payout.

[zoro]

HOw many times have you noticed this?

It was one time back in the old pybot days. I have sent the extra payment back then as well.

I’m happy to absorb the cost of this payout.

Please reconsider! We (users) cannot make profit by exploiting any bug or malfunction of NU.
We are businessmen, not adventurers

[masterOfDisaster]

@zoro, using

BAs6fhm6bfJ1b6LGnDQwah1C8frfVjjWhm

should be safe

+100 honor points granted to @zoro

[woolly_sammoth]

good point well made.
The payout address of the pool would be the one to use BAs6fhm6bfJ1b6LGnDQwah1C8frfVjjWhm

I’m glad the last time was back in pybot days. indicates that the error truly was with me and not the software. Had palpitations for a second or two when I read your initial post

[masterOfDisaster]

Had palpitations for a second or two when I read your initial post

Hearbeat back to normal?

[zoro]

use BAs6fhm6bfJ1b6LGnDQwah1C8frfVjjWhm

sent 5.359nbt.

+100 honor points granted to @zoro

these are more valuable that the whole NU reserve

[woolly_sammoth]

You are a Gent. Thank you

[huafei]

and i will pay back soon

[masterOfDisaster]

+100 honor points granted to @huafei

[Nagalim]

I also will pay back.
(And thus begins the sybil attack on honor points)

[masterOfDisaster]

+100 honor points granted to @Nagalim

[Nagalim]

Ha! Success!

If i attain honor points dishonorably, are they worth less sentiment?

[masterOfDisaster]

Ha! Success!

Oh no!
We need to install the “Advogato Trust Metric” module for Discourse.
This has top priority!

If i attain honor points dishonorably, are they worth less sentiment?

You can’t attain honor points dishonorably.
Honor is of type signed int and if you choose the dishonorable road, the result gets multiplied with -1, which leads to
-100 honor points granted to @Nagalim

[huafei]

i think nubot is still not prepare to do a pool server

txid:18a608bd8ec08f0dfe41c0603d64a7f0bdff9cb86476cc3e6049b808c7ff066c

[woolly_sammoth]

I’ve made some major changes to the price feed structure on the ALP server. It now uses far fewer socket connections to try and connect to the Nu price Streaming server so this should be the end of the price feed borking. I’ve also made the fault tolerance much better so that all errors I could think of will be caught properly and not cause a thread error. The standard price feeds now undertake a sanity check in a similar way to Nubot so a faulty bitfinex feed won;t send the pool off on a wrong price.
I’m also saving prices to the database as they come in rather than relying on object properties to save prices as this appears not to work for displaying prices in the ‘front-end’ json output. It also means we now have data on minute by minute prices on the supported exchanges/pairs.
I’ve also added the price in nbt/btc and btc/nbt as requested

I’ll continue to mi=onitor and please do mention anythhing that looks odd or you’d like to see different

[Vogger]

Does anyone know the reason for such high swings on liquidity, for this pool? I’ve seen it go up to 27k down to 15k to just 60 in “rank_1”. Is there something I am missing?