NuPond

Liquidity Pools
#162

So I’m not sure why you’re seeing that. Here are the two addresses that have been paying out the last couple days:

http://blockexplorer.nu/address/B8DZADD7UrMkzEmTWyvn2cEoxcnog1D8MK/1/newest
http://blockexplorer.nu/address/BFqe2tA4wJyDsP2CG2yDtki4wpTzSaAgfX/1/newest

As you can see, there is 1 send from each each day, corresponding to the two pools. As you say, one of those pairs of sends seems to fail, so I’m definitely not double paying. Weird that you see that, I’ll check my records and logs later today.

#163

@zoro @nmei Can I get confirmation that the CNY pool did not pay out properly today? I have the credit file, the bot thinks the payout went just dandy, so not sure what happened there. I think it’s cause I started the two scripts so close together in time, so if I just restart the CNY pool and do the payouts everything should be good.

#164

I don’t use CNY pool for some days now, sorry.

#165

ok, thanks, no problem.

I did a restart and payout, but I’m still sitting on a 20 NBT txn that I have a credit file for but can’t find on the block explorer.

#166

The double send thing @Zoro pointed out is still happening. My wallet on NuPond isn’t responding to ‘getbalance’ properly, though ‘listunspent’ matches the block explorer just fine. When I use ‘getbalance’, I actually get a different number if I use “” as the account versus not listing an account (both numbers are wrong). When I use ‘listaccounts’ it tells me “” is the only account.

Is there a way to reload my wallet or something? I know I can dump the private keys from this wallet and make a new one that will have the correct balances, but is there a more automated or convenient way to fix a misbehaving wallet?

#167

I receive payment about 3 hr ago.

#168

two payment from two address？

#169

one payment from B8DZ…

#170

Today i didn’t have a “double” payment. It isn’t actual double, just a confirmed and an (for ever) unconfirmed :slight_smile:

#171

been getting a number of double payments recently as I’ve been shifting my T1 ALP funds…

#172

I’ve done this. Let me know if there are still double payments.

#173

There is scheduled maintenance being performed on my server on 1/22/16 @ 4:30 UTC. NuPond will be down at that time, hopefully the downtime will be minimal.

#174

@Nagalim Is cny pool down ?

2016/01/17-20:05:07 ERROR: submit: socket error (timed out)
2016/01/17-20:05:09 ERROR: submit: socket error (timed out)
2016/01/17-20:05:09 ERROR: submit: socket error (104)
2016/01/17-20:05:12 ERROR: submit: socket error (104)
2016/01/17-20:05:13 ERROR: submit: socket error (timed out)
2016/01/17-20:05:17 ERROR: submit: socket error (timed out)
2016/01/17-20:05:28 ERROR: submit: socket error (timed out)
2016/01/17-20:05:28 ERROR: submit: socket error (timed out)
2016/01/17-20:05:29 ERROR: submit: socket error (timed out)
#175

Great, a new one: too many files open. Did a restart and manual payout.

Maybe i should just do a scheduled restart once a week or something.

1 Like
#176

@Nagalim OMG . turn to BTC pool…

2016/01/17-22:32:56 ERROR: submit: socket error (timed out)
2016/01/17-22:32:57 ERROR: submit: socket error (timed out)
2016/01/17-22:32:58 ERROR: submit: socket error (timed out)
2016/01/17-22:32:59 ERROR: submit: socket error (timed out)
2016/01/17-22:33:00 ERROR: submit: socket error (timed out)
2016/01/17-22:33:00 ERROR: submit: socket error (timed out)
2016/01/17-22:33:00 ERROR: submit: socket error (timed out)
2016/01/17-22:33:01 ERROR: submit: socket error (timed out)
2016/01/17-22:33:02 ERROR: submit: socket error (timed out)
2016/01/17-22:33:02 ERROR: submit: socket error (timed out)
2016/01/17-22:33:03 ERROR: submit: socket error (timed out)
2016/01/17-22:33:03 ERROR: submit: socket error (timed out)``
#177

server went down, ill restart

up again, thx for the heads up.

Got an email from my server provider saying they’re looking into the ‘health of the underlying physical node’ because of this. Hopefully it’s not a systemic incident.

#178

I see this on nbt-cny pair
2016/01/..... WARNING: unable to update BTC price from bitfinex 2016/01/..... ERROR: server price 6.yyy for cny deviates too much from price 6.xxx received from ticker, will try to delete orders on bter 2016/01/..... INFO: successfully deleted all orders for cny on bter

Are they from the nupond pool server or from my local client? @Nagalim @willy

What is this
INFO: increasing tier 1 ask limit of cny on bter from x to y
for again?

#179

still a bug not fixed …

#180

Those are two different problems. One of them originates from the price moving too swiftly and varying a lot between exchanges, and it rightly panics and deletes the orders. This usually settles down, or it kicks off the other problem.

The other issue, involving ask and bid limits, is a bug in pybot that im not going to fix. Please turn your reset_timer to 0.25 or 0.2 or so to reset every 15 min.

#181

I don’t see orders of other LPs deleted. They should unless most orders in the order book are not nupond LPs’. After repeatedly getting the error I restarted my client and the problem was totally gone. How come if it wasn’t a local problem? You are sure ISP problem (e.g. accessing bitfinex) on my side couldn’t be the cause?