Quote from: LightningJAck on January 23, 2018, 05:49:49 PM

Well i finally figured out how what others were saying about payout worked.

Then i thought about how Zpool was out of coins and then the payout scheme didnt make sense until i actually calculated a buy sell on Bittrexx and noticed the amounts to be the same.

So here is What Zpool is PROBABLY doing.

You mine 1 coin of A and get paid in .8 coin of B,
the coins are similar but with fees and all that you get less. The fees seem to not add up though.

So what i did was actually sold coin A and bought coin B with btc....
And guess what??? the coin bought was practically the same amount.

So Zpool has both coins and when you get paid in a coin they hold. They are CHARGING you the fees for if they sold what you mined and bought the coin you want payment in..

Which they are not doing as is clear by them being out of coins. So basically they are keeping the buy sell fees for themselves on top of the 2% they clear. Oh and i guess on top of the Dev Fee they now put in their
miner.

LOL

Greed is what gets you caught.

the LOL part is when you expect someone to donate you those coins instead buying them as if it was you...

Quote from: jagauthier on January 26, 2018, 04:50:11 PM

Quote from: crackfoo on January 26, 2018, 02:56:41 PM

Quote from: jagauthier on January 26, 2018, 12:23:05 PM

zpool's API has some kind of limitation on it. If you poll it too quickly it returns nothing. Thus, appearing down.

If my miner has just polled the API, and then I restart it, 9 times out of 10 the API return is blank. Yes, it's very annoying.

1 query every 10s is the limit.

Code:

2018-01-26 11:32:21,345 [ zpool][ pools][ ERROR] zpool API error. Attempt: 1/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:32:32,443 [ zpool][ pools][ ERROR] zpool API error. Attempt: 2/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:37:56,408 [ zpool][ pools][ DEBUG] Getting zpool data.
2018-01-26 11:38:58,324 [ zpool][ pools][ DEBUG] Getting zpool data.
2018-01-26 11:38:58,457 [ zpool][ pools][ ERROR] zpool API error. Attempt: 1/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:39:09,522 [ zpool][ pools][ ERROR] zpool API error. Attempt: 2/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:39:20,585 [ zpool][ pools][ ERROR] zpool API error. Attempt: 3/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:39:31,651 [ zpool][ pools][ ERROR] zpool API error. Attempt: 4/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:39:42,718 [ zpool][ pools][ ERROR] zpool API error. Attempt: 5/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:39:53,803 [ zpool][ pools][ ERROR] zpool API error. Attempt: 6/10. 'ValueError: No JSON object could be decoded'
2018-01-26 11:41:06,678 [ zpool][ pools][ DEBUG] Getting zpool data.
2018-01-26 11:42:08,561 [ zpool][ pools][ DEBUG] Getting zpool data.
2018-01-26 11:43:10,513 [ zpool][ pools][ DEBUG] Getting zpool data.
2018-01-26 11:44:12,434 [ zpool][ pools][ DEBUG] Getting zpool data.
2018-01-26 11:45:14,811 [ zpool][ pools][ DEBUG] Getting zpool data.
2018-01-26 11:46:16,708 [ zpool][ pools][ DEBUG] Getting zpool data.
2018-01-26 11:46:16,888 [ zpool][ pools][ ERROR] zpool API error. Attempt: 1/10. 'ValueError: No JSON object could be decoded'

it is obvious that your retries are exactly 10 seconds apart, make them 15-20 and it will work fine most of the time.