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

[rifleman74]

Zing!

[mercurye]

300 PH! Is this a failover or big miner coming over?

[SergES]

These blocks are not paid?

539144   2018-Aug-30 04:39   12.41098323   33.707T   200hr 23m 51s   200.67PHs   0.00%   233.931M   1.39THs   0.00008613
538852   2018-Aug-28 04:50   12.53292048   33.756T   206hr 17m 2s   195.23PHs   0.00%   195.575M   1.13THs   0.00007261
538751   2018-Aug-27 16:57   12.96019670   33.695T   207hr 11m 44s   194.02PHs   0.00%   196.793M   1.13THs   0.00007569
538670   2018-Aug-27 04:17   12.43137567   33.679T   207hr 44m 11s   193.42PHs   0.00%   207.975M   1.19THs   0.00007676
538464   2018-Aug-26 00:54   12.39296456   33.758T   208hr 24m 1s   193.26PHs   0.00%   242.576M   1.39THs   0.00008905

[VRobb]

You're just under the dust limit of 0.0001BTC per block so they're accumulating and will be payable to you once Kanosan finishes the accounting code (which he has stated will be done this year)
Mine On! 

[rifleman74]

These blocks are not paid?

539144   2018-Aug-30 04:39   12.41098323   33.707T   200hr 23m 51s   200.67PHs   0.00%   233.931M   1.39THs   0.00008613
538852   2018-Aug-28 04:50   12.53292048   33.756T   206hr 17m 2s   195.23PHs   0.00%   195.575M   1.13THs   0.00007261
538751   2018-Aug-27 16:57   12.96019670   33.695T   207hr 11m 44s   194.02PHs   0.00%   196.793M   1.13THs   0.00007569
538670   2018-Aug-27 04:17   12.43137567   33.679T   207hr 44m 11s   193.42PHs   0.00%   207.975M   1.19THs   0.00007676
538464   2018-Aug-26 00:54   12.39296456   33.758T   208hr 24m 1s   193.26PHs   0.00%   242.576M   1.39THs   0.00008905

Below dust...you need to add a bit more power to be paid with every block.

[kano]

300 PH! Is this a failover or big miner coming over?

Failover - happens with him on occasion.

[kano]

These blocks are not paid?

539144   2018-Aug-30 04:39   12.41098323   33.707T   200hr 23m 51s   200.67PHs   0.00%   233.931M   1.39THs   0.00008613
538852   2018-Aug-28 04:50   12.53292048   33.756T   206hr 17m 2s   195.23PHs   0.00%   195.575M   1.13THs   0.00007261
538751   2018-Aug-27 16:57   12.96019670   33.695T   207hr 11m 44s   194.02PHs   0.00%   196.793M   1.13THs   0.00007569
538670   2018-Aug-27 04:17   12.43137567   33.679T   207hr 44m 11s   193.42PHs   0.00%   207.975M   1.19THs   0.00007676
538464   2018-Aug-26 00:54   12.39296456   33.758T   208hr 24m 1s   193.26PHs   0.00%   242.576M   1.39THs   0.00008905

Below dust...you need to add a bit more power to be paid with every block.

They gather with the dust bunnies.
Dust bunnies will be paid out soon-ish.

[Kenni88]

BLOck Yay

[clgrissom3]

BLOck Yay

Block by andrewa44!  Welcome to the Acclaim Board with your 1st Kano block!

This is our 1st of BLOCK MONDAY!

[HSchmirPo]

andrewa44 

[BSGMiner]

andrewa44  

Wow... Got it with only 24TH/s!

"andrewa44.ant2" as in: .ant1 and .ant2, and that's it?!

Lucky dude...

P.S. - Only 0.1 block away from 100% to start the month! MINE ON!!!

[kano]

...

And you do the same thing here. Pot, meet kettle.

I deleted a follow up post of yours, not the original post of yours that is still there, of you being totally hypocritical.

You point out a web site that shows bad luck here, after previously claiming that web site is unreliable.

While you may not like me posting facts about -ck who is lying to all his miners, and you seem to think that he should be able  to hide those lies by deleting posts, I did not delete your hypocritical post that is still there for all to see your stupidity, I simply deleted your pointless follow up posts.

Edit: P.S. you left this pool and went to slush coz you threw a tizzy about people posting when we find a block.
So why are you still posting here anyway?
... and no I don't want an answer
Your post, that is still there, seems to be you telling people to leave this pool and go to slush ... and oddly enough if you do that on any pool thread, they will delete it ... though I didn't, only the pointless follow up posts

[dutchlincoln]

hi all,

Is there a good explanation for the fact that my block reward instantly declines when the pool hashrate inclines?

When i look at the pool average, its currently at 207 peta, but when i see my reward, the pool average is 219
Personally, i think that since some monster miner was added few days ago, the average is inclining according to the 5Nd rule, right? So: why are calculations for the block reward then paid at the current rate?
And who is acclaiming the difference between the 5Nd, and the current payout?

Usually when a few miners come or go, you wont notice the difference, but with a jump of 20peta, its obvios...

Anyone?

[Steamtyme]

Essentially you are getting a smaller piece of the pie, but in theory there should be more pies.

Now for slightly better explanation. You are paid a percentage of each block based on the percentage of valid shares submitted. Lets say the pool is 100PH/S (please no) and you had 10PH/S. Each block you would take in 10% of the block reward and mining fees.

Now say 100PH/S join(Some generous genius giveaway), you now only represent 5% of the total, so your reward has dropped proportionately.

Edit: Read a little more and added this, these large miners will be grabbing a portion of the reward as more of there shares are submitted, and that could look drastic when it is a large addition. Not sure what the connection is between reward hashrate and current pool hashrate at the time of the block.

Note I excluded 5nd explanation*, and assumed you are at full reward.

* I'm brutal at it.

[dutchlincoln]

Essentially you are getting a smaller piece of the pie, but in theory there should be more pies.

Now for slightly better explanation. You are paid a percentage of each block based on the percentage of valid shares submitted. Lets say the pool is 100PH/S (please no) and you had 10PH/S. Each block you would take in 10% of the block reward and mining fees.

Now say 100PH/S join(Some generous genius giveaway), you now only represent 5% of the total, so your reward has dropped proportionately.

Edit: Read a little more and added this, these large miners will be grabbing a portion of the reward as more of there shares are submitted, and that could look drastic when it is a large addition. Not sure what the connection is between reward hashrate and current pool hashrate at the time of the block.

Note I excluded 5nd explanation*, and assumed you are at full reward.

* I'm brutal at it.

this part is the obvious, but thanks for explaining.

What i mean, is that my piece of pie should decline with the 5Nd rate from previous (200 peta) to current (220 peta) in a gradual way of approx. 8 days.
This is at the moment increased to 207 peta, which is correct BUT: when i look at my payout, i see i already get a smaller pie, as it is calculated in regards to the current hashrate of 220 peta, which is not correct (yet); it should be calculated against 207 peta.

[Steamtyme]

I may as usual be wrong here, but wasn't there a large fail over temporarily bringing us up to 240? I am assuming that any large fail overs or pop ins, might be making up the difference for why the pool N average climbed faster than one would expect. As you know have the pop-ins grabbing a piece on the way out, and the new members still working to full ramp up.

That's of course just a guess, I'm sure Kano will drop some numbers and accurate information on us.

[dutchlincoln]

I may as usual be wrong here, but wasn't there a large fail over temporarily bringing us up to 240? I am assuming that any large fail overs or pop ins, might be making up the difference for why the pool N average climbed faster than one would expect. As you know have the pop-ins grabbing a piece on the way out, and the new members still working to full ramp up.

That's of course just a guess, I'm sure Kano will drop some numbers and accurate information on us.

i thought the 5Nd was created just to prevent this?

[Steamtyme]

The 5ND, would effectively prevent poolhoppers from showing up right before a block is found and earning a full reward based on their Hashrate, let's say 40PH/S but if they show up for let's say a day they would still earn on shares submitted; this may equate to something like a ramped up 5PH/S miner.

They are still entitled to get paid for the shares submitted during the 5ND.

My point was that someone large showing up for a while can raise the Pool average Hashrate, with a fairly significant impact. I think it was more noticeable because at the same time we had at least 1 other miner ramping up to 22PH/S.

[kano]

You can see part of the answer from the Pool Graph.
Yes there was an ~64PH/s failover for a number of shifts, almost 5 hours.
The rest you can see from anyone's Rewards page.

Also, the time between the last 2 blocks was 1 day + 15 minutes, so it will show a noticeable % of that failover.
Also the 5Nd range of the hash rate is not exactly 5Nd, it's randomly a bit more than 5Nd, that depends on the overflow of the last shift included to make up 5Nd.
The reward for the last block was also lower than the previous block, coz it was a short 40s network block.

Code:

Block   Block UTC          Miner Reward  N Diff   N Range        Pool N Avg
539844  2018-Sep-03 21:44  12.39446953   33.732T  185hr 26m 46s  217.01PHs
539692  2018-Sep-02 21:29  12.59554530   33.742T  189hr 58m 18s  211.90PHs

The total difference is 5.11PHs
The Miner Reward is lower, the N Diff is lower, the N Range is lower - thus the ~5hrs of 64PHs will have a slightly higher effect due to them = Pool N Avg

As per normal, the failover account themselves, will not get 64PH/s of rewards in that one block, it will be spread out over the 5Nd after they stopped.

Edit: also missed one more thing from the Pool Graph:
The Pool hash rate jumped up more than 20PHs around Aug-27 12:16

The 5Nd for 539844 was from 2018-Sep-03 21:44 back to ~Aug‑27 04:17:41 - so it only included about 8 hours of the lower pool hash rate.
The 5Nd for 539692 was from 2018-Sep-02 21:29 back to ~Aug-25 23:30:42 - so it included 1.5 days of lower hash rate.

[d57heinz]

You can see part of the answer from the Pool Graph.
Yes there was an ~64PH/s failover for a number of shifts, almost 5 hours.
The rest you can see from anyone's Rewards page.

Also, the time between the last 2 blocks was 1 day + 15 minutes, so it will show a noticeable % of that failover.
Also the 5Nd range of the hash rate is not exactly 5Nd, it's randomly a bit more than 5Nd, that depends on the overflow of the last shift included to make up 5Nd.
The reward for the last block was also lower than the previous block, coz it was a short 40s network block.

Code:

Block   Block UTC          Miner Reward  N Diff   N Range        Pool N Avg
539844  2018-Sep-03 21:44  12.39446953   33.732T  185hr 26m 46s  217.01PHs
539692  2018-Sep-02 21:29  12.59554530   33.742T  189hr 58m 18s  211.90PHs

The total difference is 5.11PHs
The Miner Reward is lower, the N Diff is lower, the N Range is lower - thus the ~5hrs of 64PHs will have a slightly higher effect due to them = Pool N Avg

As per normal, the failover account themselves, will not get 64PH/s of rewards in that one block, it will be spread out over the 5Nd after they stopped.

Edit: also missed one more thing from the Pool Graph:
The Pool hash rate jumped up more than 20PHs around Aug-27 12:16

The 5Nd for 539844 was from 2018-Sep-03 21:44 back to ~Aug‑27 04:17:41 - so it only included about 8 hours of the lower pool hash rate.
The 5Nd for 539692 was from 2018-Sep-02 21:29 back to ~Aug-25 23:30:42 - so it included 1.5 days of lower hash rate.

How many blocks has this “failover” gotten compared to his/her rewards.  That’s what I’d be most concerned about. Popping in and out is ok but at some point you better stay long enough to provide that pool a block otherwise your leaching off the fact they have a 5nd.  That’s why slush does it over one hour.  There seems there is no best solution only one in the middle with regards to pool hopping

BR