KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2438 blocks

[firetreeactual]

Just wanted to report back that I am seeing payouts!!!  Thank you all for the help, really made it easy to understand.  Been learning more in the past month then I have in all my years...Love it!!!

You're welcome, Rob. I have to agree. I've been involved with BTC since the beginning, thought I knew a lot, ended up losing a lot (for that time), and found this little alcove of practical magick last year. I continue to learn every day here.

Mine on...

[Xircom]

Did we lose out Purple Teddy bear in the red block Drama 

[wobbzz]

Interesting observation of how being offline for one hour affected my hashrate according to Kano:

10/15/2016 13:00:02 - Worker: wobbzz | 5 min: 13.277TH/s | 1 hour: 12.767TH/s | 24 hour: 12.683TH/s
10/15/2016 13:10:02 - Worker: wobbzz | 5 min: 12.460TH/s | 1 hour: 12.682TH/s | 24 hour: 12.680TH/s
10/15/2016 13:20:01 - Worker: wobbzz | 5 min: 13.855TH/s | 1 hour: 12.800TH/s | 24 hour: 12.685TH/s
10/15/2016 13:30:02 - Worker: wobbzz | 5 min: 12.804TH/s | 1 hour: 12.806TH/s | 24 hour: 12.686TH/s <- Last 10min check where I'm hashing at 100%
10/15/2016 13:40:01 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- one blade appears to have failed
10/15/2016 13:50:02 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- continued with 2 blades
wobbzz hashrate is below desired average. <- pushover notification arrived with the next API check below
10/15/2016 14:00:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- miner stopped hashing between 1350 and 1400
10/15/2016 14:10:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- apparently I
10/15/2016 14:20:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- wasn't mining
10/15/2016 14:30:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- for the last
10/15/2016 14:40:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- 24 hours
10/15/2016 14:50:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- Rebooted miner at 1452
10/15/2016 15:00:01 - Worker: wobbzz | 5 min: 10.264TH/s | 1 hour: 4.853TH/s | 24 hour: 12.035TH/s <- 24 hour hashrate credit comes back
10/15/2016 15:10:02 - Worker: wobbzz | 5 min: 12.710TH/s | 1 hour: 5.884TH/s | 24 hour: 12.035TH/s
10/15/2016 15:20:01 - Worker: wobbzz | 5 min: 13.072TH/s | 1 hour: 7.132TH/s | 24 hour: 12.048TH/s
10/15/2016 15:30:02 - Worker: wobbzz | 5 min: 14.233TH/s | 1 hour: 8.092TH/s | 24 hour: 12.055TH/s
10/15/2016 15:40:02 - Worker: wobbzz | 5 min: 12.888TH/s | 1 hour: 8.708TH/s | 24 hour: 12.057TH/s
10/15/2016 15:50:01 - Worker: wobbzz | 5 min: 14.490TH/s | 1 hour: 9.630TH/s | 24 hour: 12.075TH/s
10/15/2016 16:00:02 - Worker: wobbzz | 5 min: 14.228TH/s | 1 hour: 10.234TH/s | 24 hour: 12.084TH/s
10/15/2016 16:10:01 - Worker: wobbzz | 5 min: 13.025TH/s | 1 hour: 10.634TH/s | 24 hour: 12.091TH/s
10/15/2016 16:20:02 - Worker: wobbzz | 5 min: 13.042TH/s | 1 hour: 10.859TH/s | 24 hour: 12.090TH/s
10/15/2016 16:30:01 - Worker: wobbzz | 5 min: 13.065TH/s | 1 hour: 11.138TH/s | 24 hour: 12.093TH/s
10/15/2016 16:40:02 - Worker: wobbzz | 5 min: 12.104TH/s | 1 hour: 11.164TH/s | 24 hour: 12.088TH/s
10/15/2016 16:50:02 - Worker: wobbzz | 5 min: 13.308TH/s | 1 hour: 11.338TH/s | 24 hour: 12.088TH/s
10/15/2016 17:00:01 - Worker: wobbzz | 5 min: 12.559TH/s | 1 hour: 11.612TH/s | 24 hour: 12.096TH/s <- 2 hours later my 1hr hashrate not correct.

I don't fully understand PPLNS and don't have the time to research it right now. Does this seem correct? Would I have been paid out for 2+ blocks if they were found within the window where Kano shows my 24hr hash rate as 0?

[philipma1957]

Interesting observation of how being offline for one hour affected my hashrate according to Kano:

10/15/2016 13:00:02 - Worker: wobbzz | 5 min: 13.277TH/s | 1 hour: 12.767TH/s | 24 hour: 12.683TH/s
10/15/2016 13:10:02 - Worker: wobbzz | 5 min: 12.460TH/s | 1 hour: 12.682TH/s | 24 hour: 12.680TH/s
10/15/2016 13:20:01 - Worker: wobbzz | 5 min: 13.855TH/s | 1 hour: 12.800TH/s | 24 hour: 12.685TH/s
10/15/2016 13:30:02 - Worker: wobbzz | 5 min: 12.804TH/s | 1 hour: 12.806TH/s | 24 hour: 12.686TH/s <- Last 10min check where I'm hashing at 100%
10/15/2016 13:40:01 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- one blade appears to have failed
10/15/2016 13:50:02 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- continued with 2 blades
wobbzz hashrate is below desired average. <- pushover notification arrived with the next API check below
10/15/2016 14:00:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- miner stopped hashing between 1350 and 1400
10/15/2016 14:10:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- apparently I
10/15/2016 14:20:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- wasn't mining
10/15/2016 14:30:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- for the last
10/15/2016 14:40:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- 24 hours
10/15/2016 14:50:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- Rebooted miner at 1452
10/15/2016 15:00:01 - Worker: wobbzz | 5 min: 10.264TH/s | 1 hour: 4.853TH/s | 24 hour: 12.035TH/s <- 24 hour hashrate credit comes back
10/15/2016 15:10:02 - Worker: wobbzz | 5 min: 12.710TH/s | 1 hour: 5.884TH/s | 24 hour: 12.035TH/s
10/15/2016 15:20:01 - Worker: wobbzz | 5 min: 13.072TH/s | 1 hour: 7.132TH/s | 24 hour: 12.048TH/s
10/15/2016 15:30:02 - Worker: wobbzz | 5 min: 14.233TH/s | 1 hour: 8.092TH/s | 24 hour: 12.055TH/s
10/15/2016 15:40:02 - Worker: wobbzz | 5 min: 12.888TH/s | 1 hour: 8.708TH/s | 24 hour: 12.057TH/s
10/15/2016 15:50:01 - Worker: wobbzz | 5 min: 14.490TH/s | 1 hour: 9.630TH/s | 24 hour: 12.075TH/s
10/15/2016 16:00:02 - Worker: wobbzz | 5 min: 14.228TH/s | 1 hour: 10.234TH/s | 24 hour: 12.084TH/s
10/15/2016 16:10:01 - Worker: wobbzz | 5 min: 13.025TH/s | 1 hour: 10.634TH/s | 24 hour: 12.091TH/s
10/15/2016 16:20:02 - Worker: wobbzz | 5 min: 13.042TH/s | 1 hour: 10.859TH/s | 24 hour: 12.090TH/s
10/15/2016 16:30:01 - Worker: wobbzz | 5 min: 13.065TH/s | 1 hour: 11.138TH/s | 24 hour: 12.093TH/s
10/15/2016 16:40:02 - Worker: wobbzz | 5 min: 12.104TH/s | 1 hour: 11.164TH/s | 24 hour: 12.088TH/s
10/15/2016 16:50:02 - Worker: wobbzz | 5 min: 13.308TH/s | 1 hour: 11.338TH/s | 24 hour: 12.088TH/s
10/15/2016 17:00:01 - Worker: wobbzz | 5 min: 12.559TH/s | 1 hour: 11.612TH/s | 24 hour: 12.096TH/s <- 2 hours later my 1hr hashrate not correct.

I don't fully understand PPLNS and don't have the time to research it right now. Does this seem correct? Would I have been paid out for 2+ blocks if they were found within the window where Kano shows my 24hr hash rate as 0?

 not the right spot to look

look here  see what you have. notice I had a drop  on the left .

 I still was paid  the drop was short/

[wobbzz]

Interesting observation of how being offline for one hour affected my hashrate according to Kano:

10/15/2016 13:00:02 - Worker: wobbzz | 5 min: 13.277TH/s | 1 hour: 12.767TH/s | 24 hour: 12.683TH/s
10/15/2016 13:10:02 - Worker: wobbzz | 5 min: 12.460TH/s | 1 hour: 12.682TH/s | 24 hour: 12.680TH/s
10/15/2016 13:20:01 - Worker: wobbzz | 5 min: 13.855TH/s | 1 hour: 12.800TH/s | 24 hour: 12.685TH/s
10/15/2016 13:30:02 - Worker: wobbzz | 5 min: 12.804TH/s | 1 hour: 12.806TH/s | 24 hour: 12.686TH/s <- Last 10min check where I'm hashing at 100%
10/15/2016 13:40:01 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- one blade appears to have failed
10/15/2016 13:50:02 - Worker: wobbzz | 5 min: 8.457TH/s | 1 hour: 12.192TH/s | 24 hour: 12.660TH/s <- continued with 2 blades
wobbzz hashrate is below desired average. <- pushover notification arrived with the next API check below
10/15/2016 14:00:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- miner stopped hashing between 1350 and 1400
10/15/2016 14:10:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- apparently I
10/15/2016 14:20:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- wasn't mining
10/15/2016 14:30:01 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- for the last
10/15/2016 14:40:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- 24 hours
10/15/2016 14:50:02 - Worker: wobbzz | 5 min: 0.000TH/s | 1 hour: 0.000TH/s | 24 hour: 0.000TH/s <- Rebooted miner at 1452
10/15/2016 15:00:01 - Worker: wobbzz | 5 min: 10.264TH/s | 1 hour: 4.853TH/s | 24 hour: 12.035TH/s <- 24 hour hashrate credit comes back
10/15/2016 15:10:02 - Worker: wobbzz | 5 min: 12.710TH/s | 1 hour: 5.884TH/s | 24 hour: 12.035TH/s
10/15/2016 15:20:01 - Worker: wobbzz | 5 min: 13.072TH/s | 1 hour: 7.132TH/s | 24 hour: 12.048TH/s
10/15/2016 15:30:02 - Worker: wobbzz | 5 min: 14.233TH/s | 1 hour: 8.092TH/s | 24 hour: 12.055TH/s
10/15/2016 15:40:02 - Worker: wobbzz | 5 min: 12.888TH/s | 1 hour: 8.708TH/s | 24 hour: 12.057TH/s
10/15/2016 15:50:01 - Worker: wobbzz | 5 min: 14.490TH/s | 1 hour: 9.630TH/s | 24 hour: 12.075TH/s
10/15/2016 16:00:02 - Worker: wobbzz | 5 min: 14.228TH/s | 1 hour: 10.234TH/s | 24 hour: 12.084TH/s
10/15/2016 16:10:01 - Worker: wobbzz | 5 min: 13.025TH/s | 1 hour: 10.634TH/s | 24 hour: 12.091TH/s
10/15/2016 16:20:02 - Worker: wobbzz | 5 min: 13.042TH/s | 1 hour: 10.859TH/s | 24 hour: 12.090TH/s
10/15/2016 16:30:01 - Worker: wobbzz | 5 min: 13.065TH/s | 1 hour: 11.138TH/s | 24 hour: 12.093TH/s
10/15/2016 16:40:02 - Worker: wobbzz | 5 min: 12.104TH/s | 1 hour: 11.164TH/s | 24 hour: 12.088TH/s
10/15/2016 16:50:02 - Worker: wobbzz | 5 min: 13.308TH/s | 1 hour: 11.338TH/s | 24 hour: 12.088TH/s
10/15/2016 17:00:01 - Worker: wobbzz | 5 min: 12.559TH/s | 1 hour: 11.612TH/s | 24 hour: 12.096TH/s <- 2 hours later my 1hr hashrate not correct.

I don't fully understand PPLNS and don't have the time to research it right now. Does this seem correct? Would I have been paid out for 2+ blocks if they were found within the window where Kano shows my 24hr hash rate as 0?

 not the right spot to look

look here  see what you have. notice I had a drop  on the left .

 I still was paid  the drop was short/

There shouldn't be a "right spot to look". I pulled the data from the API, so it should reflect as accurately as the graph. It's raw data.

[kano]

...
There shouldn't be a "right spot to look". I pulled the data from the API, so it should reflect as accurately as the graph. It's raw data.

Phil is correct.

This is actually a rather important distinction about the web data I provide vs certain other pools.

If anyone used my S1/S2/S3 releases they will have seen I added at the top of the data a number "Paid GH/s"
This is the only number that matters when you mine everywhere, and it's based on accepted shares.

On the web pages: the Rewards, Shifts, Shift Graph, Pool Graph are all exact numbers, not estimates.
They are what you are paid.
"Hash Rate" here and on any pool is an estimate, not 'exactly' what you are being paid.

It doesn't matter whose version of cgminer you run, or what pool you look at, it's not the "Hash Rate" estimate that matters, what matters is the Accepted shares over each time frame you are rewarded.
The Shifts page shows that the best, and the Shift Graph is a visual display of that same data.

[wmabern]

Come on BLOCKSSSSSSSSSSSSSSSS!!!!!!  

EDIT: The pool needs more JUICE! Like about 10PH more. This is the lowest it's been since I've been a member.

[philipma1957]

...
There shouldn't be a "right spot to look". I pulled the data from the API, so it should reflect as accurately as the graph. It's raw data.

Phil is correct.

This is actually a rather important distinction about the web data I provide vs certain other pools.

If anyone used my S1/S2/S3 releases they will have seen I added at the top of the data a number "Paid GH/s"
This is the only number that matters when you mine everywhere, and it's based on accepted shares.

On the web pages: the Rewards, Shifts, Shift Graph, Pool Graph are all exact numbers, not estimates.
They are what you are paid.
"Hash Rate" here and on any pool is an estimate, not 'exactly' what you are being paid.

It doesn't matter whose version of cgminer you run, or what pool you look at, it's not the "Hash Rate" estimate that matters, what matters is the Accepted shares over each time frame you are rewarded.
The Shifts page shows that the best, and the Shift Graph is a visual display of that same data.

I remember in 2012 when I was new and asking questions .

Been here a while now. Less questions to ask.i know your setup a bit more.

[kano]

I'll add a reminder about that also from another recent post.

The number that matters about polling the API to see if a miner is OK, is the time since last share accepted "w_lastshareacc:N"

Here's the first worker from my API call

Code:

{"STAMP":"1476575097","rows":"10",
"workername:0":"Kano.A6","difficultydefault:0":"0","w_hashrate5m:0":"3178848226102.965820",
"w_hashrate1hr:0":"3113510633059.657227","w_hashrate24hr:0":"2147570918610.853516",
"w_elapsed:0":"2039775","w_lastshare:0":"1476575092","w_lastshareacc:0":"1476575092",
"w_lastdiff:0":"2496.000000","w_diffacc:0":"33527438.000000","w_diffinv:0":"113794.000000",
"w_diffsta:0":"112752.000000","w_diffdup:0":"1042.000000","w_diffhi:0":"0.000000",
"w_diffrej:0":"0.000000","w_shareacc:0":"13441.000000","w_shareinv:0":"46.000000",
"w_sharesta:0":"45.000000","w_sharedup:0":"1.000000","w_sharehi:0":"0.000000",
"w_sharerej:0":"0.000000","w_active_diffacc:0":"199680.000000","w_active_start:0":"1476574811","w_instances:0":"1",
...

For any single miner, 60 seconds since last share would be the time to send an alert.
So in the above when "STAMP":"1476575097" - "w_lastshareacc:0":"1476575092" is >= 60

For a single miner, 30s is expected to happen, on average, 3 times a day.
60s is expected to happen, on average, about once every 7 years per miner.

See more details here: (and why you may want to use 120s)
https://bitcointalk.org/index.php?topic=789369.msg15998156#msg15998156

Edit: notice that there are 2 fields "w_lastshareacc:N" and "w_lastshare:N"
The "w_lastshareacc:N" field is the important one, since if your miner goes into convulsions and starts sending unacceptable shares, the other field will still update.

[kano]

Thanks to the person who pointed 1PH at my Kano account for a while (~1.6G accepted diff)
Much appreciated

[wobbzz]

I'll add a reminder about that also from another recent post.

The number that matters about polling the API to see if a miner is OK, is the time since last share accepted "w_lastshareacc:N"

Here's the first worker from my API call

Code:

{"STAMP":"1476575097","rows":"10",
"workername:0":"Kano.A6","difficultydefault:0":"0","w_hashrate5m:0":"3178848226102.965820",
"w_hashrate1hr:0":"3113510633059.657227","w_hashrate24hr:0":"2147570918610.853516",
"w_elapsed:0":"2039775","w_lastshare:0":"1476575092","w_lastshareacc:0":"1476575092",
"w_lastdiff:0":"2496.000000","w_diffacc:0":"33527438.000000","w_diffinv:0":"113794.000000",
"w_diffsta:0":"112752.000000","w_diffdup:0":"1042.000000","w_diffhi:0":"0.000000",
"w_diffrej:0":"0.000000","w_shareacc:0":"13441.000000","w_shareinv:0":"46.000000",
"w_sharesta:0":"45.000000","w_sharedup:0":"1.000000","w_sharehi:0":"0.000000",
"w_sharerej:0":"0.000000","w_active_diffacc:0":"199680.000000","w_active_start:0":"1476574811","w_instances:0":"1",
...

For any single miner, 60 seconds since last share would be the time to send an alert.
So in the above when "STAMP":"1476575097" - "w_lastshareacc:0":"1476575092" is >= 60

For a single miner, 30s is expected to happen, on average, 3 times a day.
60s is expected to happen, on average, about once every 7 years per miner.

See more details here: (and why you may want to use 120s)
https://bitcointalk.org/index.php?topic=789369.msg15998156#msg15998156

Edit: notice that there are 2 fields "w_lastshareacc:N" and "w_lastshare:N"
The "w_lastshareacc:N" field is the important one, since if your miner goes into convulsions and starts sending unacceptable shares, the other field will still update.

Thanks Kano. I remember and appreciate your input back in August, however my concern is not entirely that my miner will completely stop. It's that I'll be operating in a reduced capacity for some time and not realize it. This is why I check the hash rate, and not the time since last share. It's my understanding that even if one blade of my miner goes down, I'm still operating at 66% capacity and will be submitting shares. Would time since last share field still be a good indicator in this situation?

[kano]

...
Thanks Kano. I remember and appreciate your input back in August, however my concern is not entirely that my miner will completely stop. It's that I'll be operating in a reduced capacity for some time and not realize it. This is why I check the hash rate, and not the time since last share. It's my understanding that even if one blade of my miner goes down, I'm still operating at 66% capacity and will be submitting shares. Would time since last share field still be a good indicator in this situation?

Nope, in that case it wont help you with any certainty.

The pool adjusts the share rate to be 18 SPM, so the share diff changing by a large amount would be one way to identify it.
However, I'm not sure how quickly that changes, and it also has to be over a certain % before ckpool will change it.

The real issue though is that you can't tell, conclusively from the shares submitted, that a miner hash rate has dropped, for quite a while after the event.
The board failing would be known to cgminer, but that also depends on what Bitmain has is their API answers.

I guess the problem here is buying unreliable hardware and trying to make it less unreliable ...
Maybe Bitmain should consider making reliable hardware, with something like 100Million$ they make each year ...

The pool hash rate is based upon shares, so you can only detect a partial failure based on a slow to determine hash rate.
Monitoring the cgminer API, assuming Bitmain has made the appropriate information available, is your only way to identify that quickly.

[Xircom]

And wmabern (The Purple Teddy Bear)  is back. Nice to see you again

[kano]

In case anyone noticed ... CKDB is restarting at the moment and should be finished restarting shortly.
There's a locking bug in the new code, I'll fix it shortly, it reports in detail what the problem is.
CKDB will be back up in a few minutes.
No miners were affected.

CKDB auto restart completed.
It identified the lock problem at 10:57:38 UTC and exited at 10:58:39 UTC
Restart completed at 11:06:17 UTC (~8.5mins - it was a full hour reload)

OK I've updated the code with the necessary fix.
I'll restart CKDB right now, since it's a specific web access that causes it and probably only one person has done it since the last restart.
The restart will be fast also since the last shift ended 1 minute after the hour.
Restarting ...

CKDB restart completed - bug update applied.
Restart was from 11:45:04 UTC to 11:52:11 UTC (~7mins)
As per normal, no miners were affected.

[wmabern]

And wmabern (The Purple Teddy Bear)  is back. Nice to see you again

LOL. I saw your post on the last page but didn't relate it to me.

I haven't gone anywhere and have been here the whole time. Except on the day when Hurricane Mathew's rain bands were hitting my house and I had to shut down and close my windows.

BTW, the bear is a Grateful Dead "Dancing Bear" and not a "teddy bear"  . I'm a Dead Head from way back and saw my first Grateful Dead show in 1977!  

EDIT: I've got a tattoo of the same bear on my arm except he is carrying a rose.

[ARXANGEL]

I'm on pool many time and at once with low power find block on pplns, but don't know that Kano put a pig to all of us.
Very good, that blocks accepted without comissions by pool.
But how we can spend this bitcoins? I try to move 1btc, but transaction weight about 100kb, because so many inputs. It's the biggest comission.
I think it not more good as SPV mining with empty blocks. Blocks with synthetical rubbish - analog of empty blocks for network.
For miners pool Kano is pool with hide comission about 5-10% for use mining bitcoins by time.
Of course, if you power more big - this comission less, but for big money you need less inputs too.
Therefore people go out from pool, because china frends not so honest, but not do this harm to their miners and network at all.
Pool is vitally important minimal limit settings for output.

[ZACHM]

I think Google translate may have missed a few things in that one.
Not really sure what is going on.  

Anyone going to try and decipher that?

[citronick]

Thanks to the person who pointed 1PH at my Kano account for a while (~1.6G accepted diff)
Much appreciated

Hope we get some more 1PH visits soon.... 

[wmabern]

I'm on pool many time and at once with low power find block on pplns, but don't know that Kano put a pig to all of us.
Very good, that blocks accepted without comissions by pool.
But how we can spend this bitcoins? I try to move 1btc, but transaction weight about 100kb, because so many inputs. It's the biggest comission.
I think it not more good as SPV mining with empty blocks. Blocks with synthetical rubbish - analog of empty blocks for network.
For miners pool Kano is pool with hide comission about 5-10% for use mining bitcoins by time.
Of course, if you power more big - this comission less, but for big money you need too less inputs.
Therefore people go out from pool, because china frends not so honest, but not do this harm to their miners and network at all.
Pool is vitally important minimal limit settings for output.

You should post your question or statement in your native language and let one of our multi-lingual members translate for you. I do not understand your post.

[firetreeactual]

And wmabern (The Purple Teddy Bear)  is back. Nice to see you again

LOL. I saw your post on the last page but didn't relate it to me.

I haven't gone anywhere and have been here the whole time. Except on the day when Hurricane Mathew's rain bands were hitting my house and I had to shut down and close my windows.

BTW, the bear is a Grateful Dead "Dancing Bear" and not a "teddy bear"  . I'm a Dead Head from way back and saw my first Grateful Dead show in 1977!  

EDIT: I've got a tattoo of the same bear on my arm except he is carrying a rose.

OMG...I knew that about the bear, but wasn't gonna say anything...another DeadHead! Mine Rock on!