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

[dance191]

p.s. Nice to see a healthy jump in the coin price for the day. I was a bit surprised when I looked today after work.

Yup...and it just keeps creeping up...wonder wassup.  

I am holding more coins then usual maybe we get a good push up  in price.

With 34PH and less blocks than usual... the bump up in BTC is a good consolation.

In the short term, I worry about that 100 block marker now touching 31.8days... 23-25 days was perfect!

Overall, we are still above 100% "lucky" compared to PPS pool, but we badly need to improve 50 and 100 blocks markers.

The only way to fix this is for our boys to come back to Kano pool and make it around 50ish PH once more. I hope Jays86 and the other big PHs farms come back soon, missing those 11-block days desperately.

Keeep calm and mine on!

Personally, as long as we mine a couple of blocks a week, I am good.  I only care about luck being as close to 100% as possible.  It appears people have left lately, and they have taken the bad luck with them (with the exception of Jays86 and maybe a few others).

Well, for the sake of the pool devs I don't want the pool to be small.  However, if we get just a steady 1 payout a week that is fine with me.  I would take 1 payout a week and good luck versus tons of payouts and bad luck.  To me the two are not even comparable.  Pool luck is the only thing that matters, everything else is optional. 

[1714553538]

1714553538

[1714553538]

1714553538

[1714553538]

1714553538

[1714553538]

1714553538

[tbonetony]

@kano

I am relearning java that I dropped long time ago. As an exercise, I am writing a small app to simply parse json data from your pool api. I would like to understand what's the limit that I can query worker stats, i.e. 1hz?

also do you have simple descriptions for returned json keys? I can guess most of them but a check would help.

Thanks.

[medo535]

Kano if you please , when I usually get paid by kano.is , I'm using my btc address as a worker, 4.5TH

When I create the txn is when the block matures as per https://kano.is/index.php?k=payout
The txn will be confirmed by our next block after that.

Thank you for replying!

[kano]

Block by jmww a little while ago

[kano]

@kano

I am relearning java that I dropped long time ago. As an exercise, I am writing a small app to simply parse json data from your pool api. I would like to understand what's the limit that I can query worker stats, i.e. 1hz?

also do you have simple descriptions for returned json keys? I can guess most of them but a check would help.

Thanks.

There's no reason to ever poll any pool for data more than once a minute

No pool hash rate is accurate since it's not possible to even know the hash rate accurately, but after about an hour it should be close.
The hash rates are only updated once per minute also, coz as explained above, there's no point updating them more often.

Thus knowing a miner is dead, the fastest would be based on when the last share was sent to the pool.
A proper miner, will on average, take more than 30s for a share about 3 times a day.

Thus the 1 minute number.

More detailed mathematical explanation here:
https://bitcointalk.org/index.php?topic=789369.msg15998156#msg15998156

I set ckdb to automatically reject all your requests for a period of time, if you access it too often.

---

The api data:

Without worker data:
https://bitbucket.org/ckolivas/ckpool/src/ff8f097cc9c0472f758bf5e0521b9629861b51ba/pool/page_api.php?at=master&fileviewer=file-view-default#page_api.php-39
which comes from
https://bitbucket.org/ckolivas/ckpool/src/ff8f097cc9c0472f758bf5e0521b9629861b51ba/src/ckdb_cmd.c?at=master&fileviewer=file-view-default#ckdb_cmd.c-3390
which is most of the page header on the web site after you login.

With worker data, it's most of:
https://bitbucket.org/ckolivas/ckpool/src/ff8f097cc9c0472f758bf5e0521b9629861b51ba/pool/page_workers.php?at=master&fileviewer=file-view-default#page_workers.php-77
which also matches the workers page on the web site but includes more time ranges for the hash rate.

Otherwise, ask me here what a field is, by name.

[clgrissom3]

Block by 16hNunxPK!  This is his 3rd Kano block and our 3rd of the day!  What a good wake up call! 

[hhumaidan]

4

[clgrissom3]

4

Yes, block by dance191!  This is his 17th Kano block and our 4th of the day! 

[philipma1957]

block

damn too slow

[clgrissom3]

block

damn too slow

I was too slow also; hhumaidan beat me to the punch this time! 

I am really glad to see our Last 500 Blocks back up over 100% on the Block Statistics page! 

[HerbPean]

block

damn too slow

I was too slow also; hhumaidan beat me to the punch this time! 

I am really glad to see our Last 500 Blocks back up over 100% on the Block Statistics page! 

Luck is good since a few days ! Quite a nice run we are having here, especially from the previous bad luck.

[firetreeactual]

Well, It's noisier here in the living room datacenter with the S3s back up, but hashing almost at the old rate.

Really nice to wake up to four blocks.  

EDIT: There's an old Hawaiian shaman lives down the road here...he and I meet up once in a while just to "talk story." Sky Pilot and I are gonna go see him this afternoon and see what he can do for the blocks. I'd take him a chicken, but there's hundreds of them running around here feral and it would be an empty gesture, methinks.

But then, a bottle of Glenlivet might help...

[philipma1957]

What happened? We seemed to have tanked.

what do you mean by that?

we are at 174% luck over the last 5 blocks

and the current block is still very low for shares  120,000,000,000 is low  255,000,000,000 is average luck to make a block

[citronick]

What happened? We seemed to have tanked.

what do you mean by that?

we are at 174% luck over the last 5 blocks

and the current block is still very low for shares  120,000,000,000 is low  255,000,000,000 is average luck to make a block

I think he meant 50PHs.... to 34PHs.

But as far as luck is concerned, the number of small miners solving blocks in the past few days alone shows luck factor is very strong in planet kano.

But I still miss those 7blocks - 11blocks days...

[Xircom]

p.s. Nice to see a healthy jump in the coin price for the day. I was a bit surprised when I looked today after work.

Yup...and it just keeps creeping up...wonder wassup. 

I am holding more coins then usual maybe we get a good push up  in price.

With 34PH and less blocks than usual... the bump up in BTC is a good consolation.

In the short term, I worry about that 100 block marker now touching 31.8days... 23-25 days was perfect!

Overall, we are still above 100% "lucky" compared to PPS pool, but we badly need to improve 50 and 100 blocks markers.

The only way to fix this is for our boys to come back to Kano pool and make it around 50ish PH once more. I hope Jays86 and the other big PHs farms come back soon, missing those 11-block days desperately.

Keeep calm and mine on!

You got that right Citronick, we need those extra 10PH. 31,8 days pr 100 blocks is just not enough. I still do think we are able to creep up and tomorrow I hope I will have extra 100TH up running if Fedex delivers in time. No doubt that a new miner has entered the marked the last 1.5 week with those diff peaks. Just wonder if it is a new Bitmain geneartion or Canan. I just do not think Canan will be ready on this site of new year with the latest reports re. not going together with the other chinese company.

[philipma1957]

Well I end my diff threads  but  diff is dropping nicely  so far  and price is going up.  Along with really solid luck at the moment.

This is a nice trifecta for us.

1)CoinBase at 639 usd.


2)




3)

[ZACHM]

It could have been the end of a shift or a block was found on the network so the pool needed to send workers the new block info to work on and it takes a few seconds for everyone to switch over. Nothing to be concerned about.

[firetreeactual]

I have a miner at home and a miner in my office (28 miles apart) and both showed a "Share Rate" of 0 for a few minutes on the Workers page. At that same time our Pool rate went from 33.7x to sub 33 and was diving. The dive was starting to look ugly. That's what I was talking about. Anyway I got busy, then I just got back to it and looked to see both miners hashing away at their normal rates. So what causes hashing to drop off like this?

Zach got to it first...ditto. No worries.

[swilla]

block!

[firetreeactual]

Well...it's a five-block day so far, and my per block rewards are up about 18% even with the S3s filling in...so I'm not unhappy at all.

Mine on...