block
damn too slow
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1208. (Read 5352229 times)
October 12, 2016, 08:18:12 AM
October 12, 2016, 08:17:53 AM
4
Yes, block by dance191! This is his 17th Kano block and our 4th of the day!
October 12, 2016, 08:17:19 AM
4
October 12, 2016, 07:59:06 AM
Block by 16hNunxPK! This is his 3rd Kano block and our 3rd of the day! What a good wake up call!
October 12, 2016, 05:40:30 AM
@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 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.
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://bitcointalksearch.org/topic/m.15998156
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.
October 12, 2016, 05:15:28 AM
Block by jmww a little while ago
October 12, 2016, 04:40:37 AM
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=payoutThe txn will be confirmed by our next block after that.
Thank you for replying!
October 12, 2016, 03:45:53 AM
@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.
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.
October 12, 2016, 02:20:03 AM
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.
October 12, 2016, 12:40:56 AM
Block by 659miners
October 12, 2016, 12:04:21 AM
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!
1) the 715% (+221%) block
2) the run of five 300-400% blocks out of eleven, 1436-1446
These things happen, and the hash rate wont make any difference to if they will happen.
More or less miners wont change luck, only how long bad luck lasts, and how short good luck lasts.
If bad luck passes more quickly, so does good luck pass more quickly.
Higher hash rate = lower variance = shorter time for a bad luck block = shorter time for a good luck block.
Statistically, the expected result is the same.
While we are still averaging more than a block a day, there shouldn't be much of an effect on reward variance unless you are a short term miner.
October 11, 2016, 09:32:55 PM
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!
October 11, 2016, 08:51:08 PM
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.
October 11, 2016, 08:35:30 PM
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.
October 11, 2016, 06:54:41 PM
Looks like I'm losing two boards on one of my S9's. &%$$##$^&&**&^%$$###$%$%$#$$%^!
Rebooted a few times. It comes back all o's and after a few minutes, there are x's scattered throughout the two boards. I have just unplugged it for now and will screw with it again tomorrow. Damn it!!!!!!!!!
So my pool hash is going to be down to ~38TH until something changes.
Heat is not an issue. It's cold here now. Most of my chip temps are in the low to mid 70's. Running from a Bitmain 240v PSU. Arggggggg.
Rebooted a few times. It comes back all o's and after a few minutes, there are x's scattered throughout the two boards. I have just unplugged it for now and will screw with it again tomorrow. Damn it!!!!!!!!!
So my pool hash is going to be down to ~38TH until something changes.
Heat is not an issue. It's cold here now. Most of my chip temps are in the low to mid 70's. Running from a Bitmain 240v PSU. Arggggggg.
I had a snowstorm on Saturday through night. When I woke up in the morning my S9 on balcony was *half* buried in snow. There was a pool of water around it. I freaked out. Then I powered it up, only two board half working and it could not work longer than 15 minutes. I thought I screwed up really bad. After sun dried all day on Sunday, the two boards revived to full working state. Today I switched the data cable on the down board. hey, it came back up! I guess I am just REALLY lucky this time.
Cool. Glad it's working again, Where did you get snow?
I moved the cables around on my flakey S9 and down-clocked from 600 to 575 MHz and mine is behaving again with only a single x on one board. As long as it's averaging a little over ~12TH, I'm going to keep it running till it dies. Hopefully a while longer!
So I have ~50TH back on the pool for now.
Edit: Now the single x is gone. It will probably come and go. We shall see how it behaves in the coming hours / days.
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.
October 11, 2016, 06:48:07 PM
Looks like I'm losing two boards on one of my S9's. &%$$##$^&&**&^%$$###$%$%$#$$%^!
Rebooted a few times. It comes back all o's and after a few minutes, there are x's scattered throughout the two boards. I have just unplugged it for now and will screw with it again tomorrow. Damn it!!!!!!!!!
So my pool hash is going to be down to ~38TH until something changes.
Heat is not an issue. It's cold here now. Most of my chip temps are in the low to mid 70's. Running from a Bitmain 240v PSU. Arggggggg.
Rebooted a few times. It comes back all o's and after a few minutes, there are x's scattered throughout the two boards. I have just unplugged it for now and will screw with it again tomorrow. Damn it!!!!!!!!!
So my pool hash is going to be down to ~38TH until something changes.
Heat is not an issue. It's cold here now. Most of my chip temps are in the low to mid 70's. Running from a Bitmain 240v PSU. Arggggggg.
I had a snowstorm on Saturday through night. When I woke up in the morning my S9 on balcony was *half* buried in snow. There was a pool of water around it. I freaked out. Then I powered it up, only two board half working and it could not work longer than 15 minutes. I thought I screwed up really bad. After sun dried all day on Sunday, the two boards revived to full working state. Today I switched the data cable on the down board. hey, it came back up! I guess I am just REALLY lucky this time.
October 11, 2016, 05:45:44 PM
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=payoutThe txn will be confirmed by our next block after that.
October 11, 2016, 03:57:24 PM
Kano if you please , when I usually get paid by kano.is , I'm using my btc address as a worker, 4.5TH
October 11, 2016, 02:37:36 PM
Just got Dopey, Happy, & Bashful (3 of my 6 S3s) back up online to try to make up for the A6...that's why I kept them, actually. The free power factor makes it possible to do backups like that. I'm back to around 20TH. Don't have any amps for the rest.
Doin' what we can...
Doin' what we can...
October 11, 2016, 02:26:14 PM
Block by 1D8BtqNYbco7 with 30TH/s! This is his 2nd Kano block and our 4th of the day!
Jump to: