It really paid off this time around!EDIT: And it looks like our Block Statistics recovered nicely after the monster block made it's presence known!
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1561. (Read 5352367 times)
April 05, 2016, 08:32:22 AM
The same thing happened to me when I put in a 1PH bump to try to get past the monster block...those shifts have been paid 5 times so far and it is still within my red 5Nd zone on the chart. It looks exactly like your chart It really paid off this time around!
EDIT: And it looks like our Block Statistics recovered nicely after the monster block made it's presence known!
It really paid off this time around!EDIT: And it looks like our Block Statistics recovered nicely after the monster block made it's presence known!
April 05, 2016, 08:17:37 AM
I got very lucky with rentals again!
It has been 23 hours since I did the 2ph rental for an hour as you can see I got over .3btc back so far and I have time for one or two more blocks!
I am going to bump to 500th
It has been 23 hours since I did the 2ph rental for an hour as you can see I got over .3btc back so far and I have time for one or two more blocks!
I am going to bump to 500th
April 05, 2016, 08:00:07 AM
Block by TCSDR1 and it confirmed our payout! That is his 6th kano block!
April 05, 2016, 04:59:05 AM
There'll be a ckdb restart in about an hour.
No miners will be affected.
The web site will show lotsa '?' for about 10 minutes.
It will be just after the next shift summary after 08:00 UTC - which should be at about 08:20 UTC
This is to push in a few updates and, yet again, test the processing changes I've been testing in the previous 2 planned restarts.
Again, if there's any problems, I'll simply roll back the version.
I've resolved the 'zillions' of warning messages and the sync issues, but there's one test I'm having trouble with at home that will again need the live pool - with regards to how fast the data is coming from ckpool (which I've not been able to emulate well in home testing)
I'm delaying this another hour.No miners will be affected.
The web site will show lotsa '?' for about 10 minutes.
It will be just after the next shift summary after 08:00 UTC - which should be at about 08:20 UTC
This is to push in a few updates and, yet again, test the processing changes I've been testing in the previous 2 planned restarts.
Again, if there's any problems, I'll simply roll back the version.
I've resolved the 'zillions' of warning messages and the sync issues, but there's one test I'm having trouble with at home that will again need the live pool - with regards to how fast the data is coming from ckpool (which I've not been able to emulate well in home testing)
The last block meant I didn't estimate it correctly and it would be around 08:40 UTC - so it's better to wait for the one after it being a lot closer to just after the hour (which means a faster restart)
So the next shift summary after that will be about 09:20 UTC or a bit after.
That's when I'll do the ckdb restart.
Alas it did not solve the one outstanding problem.
However, the delay problems I'm getting at home testing are simply the way I'm testing it, they don't exist on the pool.
So only one issue left unresolved ... later for whenever the next ckdb restart is in a few days.
Edit: note: that outstanding problem has nothing to do with the CKDB crash the other day, that's been fixed.
April 05, 2016, 02:52:46 AM
There's 3 options done by different people.
A web site (zach) and 2 apps, one iApp and one Android
See the first post for the links for all 3.
A web site (zach) and 2 apps, one iApp and one Android
See the first post for the links for all 3.
April 05, 2016, 02:46:38 AM
I'm new to Kano pool, just wanna ask if there is a miner monitoring feature? Do I get email or SMS notification if the miner has rate is dropping? Thanks!
April 05, 2016, 02:19:53 AM
No miners will be affected.
The web site will show lotsa '?' for about 10 minutes.
It will be just after the next shift summary after 08:00 UTC - which should be at about 08:20 UTC
This is to push in a few updates and, yet again, test the processing changes I've been testing in the previous 2 planned restarts.
Again, if there's any problems, I'll simply roll back the version.
I've resolved the 'zillions' of warning messages and the sync issues, but there's one test I'm having trouble with at home that will again need the live pool - with regards to how fast the data is coming from ckpool (which I've not been able to emulate well in home testing)
See below.
April 05, 2016, 02:18:06 AM
4 blocks today already ! w00t !!
April 05, 2016, 01:53:22 AM
They see me rollin they hatin
Block party!
Block party!
April 05, 2016, 01:38:37 AM
... another quiet block sneaks by ... 
(Edit: 2)
(Edit: 2)
April 04, 2016, 11:25:06 PM
lets get some noisy blocks. a quick 3 or 4 will do for me.
April 04, 2016, 10:25:45 PM
... another quiet block sneaks by ...
I didn't even see it lol
April 04, 2016, 10:21:37 PM
April 04, 2016, 10:18:40 PM
... another quiet block sneaks by ...
April 04, 2016, 09:08:55 PM
Hot Damn! Didn't even see the first one, that was a rental was well worth it!
April 04, 2016, 08:09:47 PM
Block by cmwahlqu with a rental! That would be his 2nd kano block!
April 04, 2016, 07:30:59 PM
Curious mind wants to know why. If you are able to share.
There are bugs being fixed all the time in the code (along with improvements and feature enhancements). All you need to do is follow the changelogs in git as they happen since all the code on this pool is public:https://bitbucket.org/ckolivas/ckpool
April 04, 2016, 07:17:07 PM
CKDB crashed at 23:01:47 UTC
No miners were affected since it was ckdb only, not ckpool.
Since it's so big it took 10 minutes (and 11 seconds) to crash (to write the core file)
It's on it's way back up again and should be all back to normal in less than 5 more minutes.
Edit: restart complete at 23:26:07.943 UTC
Edit2: yes I am working on fixing it so it doesn't happen due to the same cause again - the core dump showed clearly why (if anyone was wondering)
No miners were affected since it was ckdb only, not ckpool.
Since it's so big it took 10 minutes (and 11 seconds) to crash (to write the core file)
It's on it's way back up again and should be all back to normal in less than 5 more minutes.
Edit: restart complete at 23:26:07.943 UTC
Edit2: yes I am working on fixing it so it doesn't happen due to the same cause again - the core dump showed clearly why (if anyone was wondering)
Curious mind wants to know why. If you are able to share.
April 04, 2016, 07:05:41 PM
If you were running Windows your core file would've just said "I fell over"
Love it when *nix boxes provide a ton of info.
And I always admire people who can read AND understand it.
April 04, 2016, 06:44:41 PM
lol
Jump to: