BLOCK 
That was a tough one at 502.797%
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1683. (Read 5352527 times)
February 27, 2016, 08:35:23 AM
February 27, 2016, 08:34:25 AM
church lady to pool Well aint that special 
February 27, 2016, 08:32:01 AM
Hi
Kano, Apologies if this turns out to be the most stupid post of the month so far.
I am just getting my head around how the pool pays by PPLNS, which while I have mined here I have seen the 5Nd period drop from 192hrs to 34hrs as the pool grows.
Never really considered this before today, because I haven't had to sat through a tough block that exceeded the 5Nd period, but I think this block hrs will be greater than the expected 5Nd payment period, which if I understand it, means were only going to get 1/5th of the payment for the last 36+ hrs, and we will loose out on any % payments that we didn't already receive from the previous found blocks, so that for some of the previous blocks we will loose 80%, 60% or 40% of the expected payments should we have continued at the expected 100% rather than this maddening 480% + block that were struggling with.
The only good thing that I can see is that the previous found blocks which we will loose the payments were all quite close together so the loss on previous payments is not so bad, but if we have another bad block as the next one, then we would be loosing 80% of a lot of hours work from this current block.
Is there a point when a pool hash rate gets larger, 20PH+ or whatever, when it hits a point when the 5Nd from the PPLNS actually works against the miners, because the smaller and smaller hrs of the 5Nd period and any bad luck wipes out any benefit of trying to even out the payments by using the 5Nd, is there a point when a pool gets to a larger size to actually run PPS, so to pay for the work done as its done, and then no-one ever looses out on the bad blocks that can over-run the 5Nd period and cause the loss of previous work done.
is PPLNS always best for any sized pool, or is PPS better for a certain sized pools.
If this is a stupid question just delete it
Steve
Kano, Apologies if this turns out to be the most stupid post of the month so far.
I am just getting my head around how the pool pays by PPLNS, which while I have mined here I have seen the 5Nd period drop from 192hrs to 34hrs as the pool grows.
Never really considered this before today, because I haven't had to sat through a tough block that exceeded the 5Nd period, but I think this block hrs will be greater than the expected 5Nd payment period, which if I understand it, means were only going to get 1/5th of the payment for the last 36+ hrs, and we will loose out on any % payments that we didn't already receive from the previous found blocks, so that for some of the previous blocks we will loose 80%, 60% or 40% of the expected payments should we have continued at the expected 100% rather than this maddening 480% + block that were struggling with.
The only good thing that I can see is that the previous found blocks which we will loose the payments were all quite close together so the loss on previous payments is not so bad, but if we have another bad block as the next one, then we would be loosing 80% of a lot of hours work from this current block.
Is there a point when a pool hash rate gets larger, 20PH+ or whatever, when it hits a point when the 5Nd from the PPLNS actually works against the miners, because the smaller and smaller hrs of the 5Nd period and any bad luck wipes out any benefit of trying to even out the payments by using the 5Nd, is there a point when a pool gets to a larger size to actually run PPS, so to pay for the work done as its done, and then no-one ever looses out on the bad blocks that can over-run the 5Nd period and cause the loss of previous work done.
is PPLNS always best for any sized pool, or is PPS better for a certain sized pools.
If this is a stupid question just delete it
Steve
If you do PPLNS anytime you rip back to back cdfs of 99% for your blocks you are fucked.. But just for the two blocks.
The key is think in 100 block segments not 2 block segments. What is the record for the last 100 blocks?
116.05% now if you did PPS at a 99% payrate for those 100 blocks you would have lost out on the 17% over the 99%.
To follow up f2pool pays 96% not 99% and f2pool takes the tx id fees. while give some NMC nets to 96% so over the last 100 blocks so if 100% was 1 btc
you would get .96 btc from f2pool maybe .97 btc
kano you would get 1.16 btc maybe 1.164 btc since he gives the tx id fees.
so .97 to 1.16 is a good estimate for a 100 block period.
But for this block right now PPS is better. Small samples of 1, 2, 3, 4 blocks do not mean much.
a cdf of .993 second best ever
bitminerpro_S3R.2059A0C51E43 thanks hey was this an s3?
February 27, 2016, 08:31:53 AM
Thank God, was getting worried
February 27, 2016, 08:31:15 AM
There it is.
February 27, 2016, 08:30:35 AM
BLOCK
Finally! Now "WE" can get on with Block Saturday, to make up for a non-block Friday..
And with 0.55687924 BTC in fee's!
February 27, 2016, 08:28:20 AM
BLOCK
February 27, 2016, 08:06:40 AM
I need a drink 
Maybe some Valium.
Maybe some Valium.
Well Yeah we are at 496% which is over a cdf of 99%.
This is the 2nd worst block in history of the pool.
I have some high quality vodka that I dropped 6 vanilla sticks into. Best vanilla vodka you could ever have.
February 27, 2016, 08:06:13 AM
i nice Chaos Calmer will do 
February 27, 2016, 08:04:37 AM
I need a drink
Maybe some Valium.
Maybe some Valium.
February 27, 2016, 08:00:02 AM
Hi
Kano, Apologies if this turns out to be the most stupid post of the month so far.
I am just getting my head around how the pool pays by PPLNS, which while I have mined here I have seen the 5Nd period drop from 192hrs to 34hrs as the pool grows.
Never really considered this before today, because I haven't had to sat through a tough block that exceeded the 5Nd period, but I think this block hrs will be greater than the expected 5Nd payment period, which if I understand it, means were only going to get 1/5th of the payment for the last 36+ hrs, and we will loose out on any % payments that we didn't already receive from the previous found blocks, so that for some of the previous blocks we will loose 80%, 60% or 40% of the expected payments should we have continued at the expected 100% rather than this maddening 480% + block that were struggling with.
The only good thing that I can see is that the previous found blocks which we will loose the payments were all quite close together so the loss on previous payments is not so bad, but if we have another bad block as the next one, then we would be loosing 80% of a lot of hours work from this current block.
Is there a point when a pool hash rate gets larger, 20PH+ or whatever, when it hits a point when the 5Nd from the PPLNS actually works against the miners, because the smaller and smaller hrs of the 5Nd period and any bad luck wipes out any benefit of trying to even out the payments by using the 5Nd, is there a point when a pool gets to a larger size to actually run PPS, so to pay for the work done as its done, and then no-one ever looses out on the bad blocks that can over-run the 5Nd period and cause the loss of previous work done.
is PPLNS always best for any sized pool, or is PPS better for a certain sized pools.
If this is a stupid question just delete it
Steve
Kano, Apologies if this turns out to be the most stupid post of the month so far.
I am just getting my head around how the pool pays by PPLNS, which while I have mined here I have seen the 5Nd period drop from 192hrs to 34hrs as the pool grows.
Never really considered this before today, because I haven't had to sat through a tough block that exceeded the 5Nd period, but I think this block hrs will be greater than the expected 5Nd payment period, which if I understand it, means were only going to get 1/5th of the payment for the last 36+ hrs, and we will loose out on any % payments that we didn't already receive from the previous found blocks, so that for some of the previous blocks we will loose 80%, 60% or 40% of the expected payments should we have continued at the expected 100% rather than this maddening 480% + block that were struggling with.
The only good thing that I can see is that the previous found blocks which we will loose the payments were all quite close together so the loss on previous payments is not so bad, but if we have another bad block as the next one, then we would be loosing 80% of a lot of hours work from this current block.
Is there a point when a pool hash rate gets larger, 20PH+ or whatever, when it hits a point when the 5Nd from the PPLNS actually works against the miners, because the smaller and smaller hrs of the 5Nd period and any bad luck wipes out any benefit of trying to even out the payments by using the 5Nd, is there a point when a pool gets to a larger size to actually run PPS, so to pay for the work done as its done, and then no-one ever looses out on the bad blocks that can over-run the 5Nd period and cause the loss of previous work done.
is PPLNS always best for any sized pool, or is PPS better for a certain sized pools.
If this is a stupid question just delete it
Steve
If you do PPLNS anytime you rip back to back cdfs of 99% for your blocks you are fucked.. But just for the two blocks.
The key is think in 100 block segments not 2 block segments. What is the record for the last 100 blocks?
116.05% now if you did PPS at a 99% payrate for those 100 blocks you would have lost out on the 17% over the 99%.
February 27, 2016, 07:16:13 AM
Hi
Kano, Apologies if this turns out to be the most stupid post of the month so far.
I am just getting my head around how the pool pays by PPLNS, which while I have mined here I have seen the 5Nd period drop from 192hrs to 34hrs as the pool grows.
Never really considered this before today, because I haven't had to sat through a tough block that exceeded the 5Nd period, but I think this block hrs will be greater than the expected 5Nd payment period, which if I understand it, means were only going to get 1/5th of the payment for the last 36+ hrs, and we will loose out on any % payments that we didn't already receive from the previous found blocks, so that for some of the previous blocks we will loose 80%, 60% or 40% of the expected payments should we have continued at the expected 100% rather than this maddening 480% + block that were struggling with.
The only good thing that I can see is that the previous found blocks which we will loose the payments were all quite close together so the loss on previous payments is not so bad, but if we have another bad block as the next one, then we would be loosing 80% of a lot of hours work from this current block.
Is there a point when a pool hash rate gets larger, 20PH+ or whatever, when it hits a point when the 5Nd from the PPLNS actually works against the miners, because the smaller and smaller hrs of the 5Nd period and any bad luck wipes out any benefit of trying to even out the payments by using the 5Nd, is there a point when a pool gets to a larger size to actually run PPS, so to pay for the work done as its done, and then no-one ever looses out on the bad blocks that can over-run the 5Nd period and cause the loss of previous work done.
is PPLNS always best for any sized pool, or is PPS better for a certain sized pools.
If this is a stupid question just delete it
Steve
Kano, Apologies if this turns out to be the most stupid post of the month so far.
I am just getting my head around how the pool pays by PPLNS, which while I have mined here I have seen the 5Nd period drop from 192hrs to 34hrs as the pool grows.
Never really considered this before today, because I haven't had to sat through a tough block that exceeded the 5Nd period, but I think this block hrs will be greater than the expected 5Nd payment period, which if I understand it, means were only going to get 1/5th of the payment for the last 36+ hrs, and we will loose out on any % payments that we didn't already receive from the previous found blocks, so that for some of the previous blocks we will loose 80%, 60% or 40% of the expected payments should we have continued at the expected 100% rather than this maddening 480% + block that were struggling with.
The only good thing that I can see is that the previous found blocks which we will loose the payments were all quite close together so the loss on previous payments is not so bad, but if we have another bad block as the next one, then we would be loosing 80% of a lot of hours work from this current block.
Is there a point when a pool hash rate gets larger, 20PH+ or whatever, when it hits a point when the 5Nd from the PPLNS actually works against the miners, because the smaller and smaller hrs of the 5Nd period and any bad luck wipes out any benefit of trying to even out the payments by using the 5Nd, is there a point when a pool gets to a larger size to actually run PPS, so to pay for the work done as its done, and then no-one ever looses out on the bad blocks that can over-run the 5Nd period and cause the loss of previous work done.
is PPLNS always best for any sized pool, or is PPS better for a certain sized pools.
If this is a stupid question just delete it
Steve
February 27, 2016, 05:52:23 AM
As many would have noticed, I also did a ckdb restart in there.
There was a syncronisation issue between ckdb and ckpool so restarting ckdb resets the synchronisation and ensures no data was lost
ckdb tracks every record and every type of record it gets from ckpool since they all have continuous sequence numbers - so with the restart, as usual, I see no sequence problems so I know the synchronisation is all correct and zero data has been skipped/lost.
(a ckdb restart goes back and reprocesses from the last completed/summarised shift, reading the last hour or more, in this case 40 minutes of shift data back before the ckpool restart, so it can be sure it's all ok)
There was a syncronisation issue between ckdb and ckpool so restarting ckdb resets the synchronisation and ensures no data was lost
ckdb tracks every record and every type of record it gets from ckpool since they all have continuous sequence numbers - so with the restart, as usual, I see no sequence problems so I know the synchronisation is all correct and zero data has been skipped/lost.
(a ckdb restart goes back and reprocesses from the last completed/summarised shift, reading the last hour or more, in this case 40 minutes of shift data back before the ckpool restart, so it can be sure it's all ok)
February 27, 2016, 05:35:49 AM
This is the update that's tried to get in for the last couple of restarts and failed each time.
Code bad, failed update, rolled back, my bad. Unknown why yet. February 27, 2016, 05:29:48 AM
Was that iambic pentameter, you make a really bad poet.
February 27, 2016, 05:27:29 AM
All miner side stats look good.
All best shares look lower than usual.
All best shares look lower than usual.
February 27, 2016, 04:33:16 AM
Well in the hope of using superstition to break this double black Friday ...
Fri 26th = 2x13
I'll be doing a pool restart in half an hour when the minute hand next hits zero.
This is the update that's tried to get in for the last couple of restarts and failed each time.
It will (hopefully) be a normal restart and you will only see a quick reconnect in your miners
- we usually find less than 1% have anything more than a quick reconnect during a normal restart.
However, there will be one other change during the restart.
I will be rebooting the DE node completely.
This will take a few minutes (at the most) so all miners on the DE node will fail over.
I picked now to do the DE restart since it's morning to the middle of the day in Europe.
Well this is the highest Diff% block so far since the 666.666% block, lets hope it doesn't make a record
Fri 26th = 2x13
I'll be doing a pool restart in half an hour when the minute hand next hits zero.
This is the update that's tried to get in for the last couple of restarts and failed each time.
It will (hopefully) be a normal restart and you will only see a quick reconnect in your miners
- we usually find less than 1% have anything more than a quick reconnect during a normal restart.
However, there will be one other change during the restart.
I will be rebooting the DE node completely.
This will take a few minutes (at the most) so all miners on the DE node will fail over.
I picked now to do the DE restart since it's morning to the middle of the day in Europe.
Well this is the highest Diff% block so far since the 666.666% block, lets hope it doesn't make a record
February 27, 2016, 02:45:37 AM
31hr and no blocks 
Have faith, we will crack one real soon
Keep calm and mine on.
February 27, 2016, 02:30:41 AM
31hr and no blocks
Have faith, we will crack one real soon
February 27, 2016, 01:50:22 AM
31hr and no blocks
Jump to: