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

[kano]

Sorry for the question that I am sure has already been asked but I can't find an answer too.

I understand that currently our payouts happen in the following block to avoid fees. I understand that we had two blocks hit back to back over the weekend (498476 and 498508) and they hit to close together to have the latter confirm the former, so they will both be payed out in our next block. My issue is I am seeing the payouts in my wallet. Why/how could that be? What am I missing?

You will see the payouts, at the latest, in our pool's block after they have matured.
The transaction is sent out once the block matures.

However, when I add a transaction fee to the payout, it can be confirmed sooner by another pool - as I usually do lately.

[1713572488]

1713572488

[2tights]

Sorry for the question that I am sure has already been asked but I can't find an answer too.

I understand that currently our payouts happen in the following block to avoid fees. I understand that we had two blocks hit back to back over the weekend (498476 and 498508) and they hit to close together to have the latter confirm the former, so they will both be payed out in our next block. My issue is I am seeing the payouts in my wallet. Why/how could that be? What am I missing?

They matured. Happy dance.

[rifleman74]

Sorry for the question that I am sure has already been asked but I can't find an answer too.

I understand that currently our payouts happen in the following block to avoid fees. I understand that we had two blocks hit back to back over the weekend (498476 and 498508) and they hit to close together to have the latter confirm the former, so they will both be payed out in our next block. My issue is I am seeing the payouts in my wallet. Why/how could that be? What am I missing?

They were sent out fairly quickly...you should already have the BTC in your wallet.  No reason to wait for the next block.   The first block wasn't in the second block because it hadn't confirmed.

[Waztim]

Since I've not posted it for a while ... here's the CDF table

Code:

 1  0.39346934028737   50.000%  1 in 1.6
 2  0.63212055882856  100.000%  1 in 2.7
 3  0.77686983985157  150.000%  1 in 4.5
 4  0.86466471676339  200.000%  1 in 7.4
 5  0.95021293163214  300.000%  1 in 20.1
 6  0.98168436111127  400.000%  1 in 54.6
 7  0.99326205300091  500.000%  1 in 148.4
 8  0.99752124782333  600.000%  1 in 403.4
 9  0.99872735771441  666.666%  1 in 785.8
10  0.99908811803445  700.000%  1 in 1096.6
11  0.99966453737210  800.000%  1 in 2981.0
12  0.99987659019591  900.000%  1 in 8103.1

What line 2 says, is that we expect, on average, 1 in 2.7 blocks, to be over 100%
What line 5 says, is that we expect, on average, 1 in 20.1 blocks, to be over 300%
etc.

It's something that a lot of people don't realise about the expected results when finding blocks

Just thought I'd post it again for the newer members

Kano,
What is the relationship between Pool Hash Rate, Diff and Probabilities, if any? Meaning as Diff Increases without Pool Hash Increase, how does that affect our Probabilities? I am thinking it only affects time to 100% Diff, your thoughts.
Thanks -Mine On 

[rifleman74]

On another note kano, on the invalid screen for workers, I understand what all of the acronyms but the "Hi" I don't know....I only get that on my S7 which isn't perfectly set up.

Anyone else can answer too. 


Stale, Duplidate "Hi" Rejected.

[Toll-Booth-Jim]

This one better have like 29 BTC in it. LoL      

[2tights]

This one better have like 29 BTC in it. LoL      

In the long run, everything evens out.

[rifleman74]

This one better have like 29 BTC in it. LoL      

Latest avgs from Slush have been 16 and change...

[rifleman74]

162.58%   Let's crack it!

[wavelengthsf]

I'm about to get in line for star wars, but I've told the miners that they better find some blocks by the time the movie is done, or else!

[kano]

Since I've not posted it for a while ... here's the CDF table

Code:

 1  0.39346934028737   50.000%  1 in 1.6
 2  0.63212055882856  100.000%  1 in 2.7
 3  0.77686983985157  150.000%  1 in 4.5
 4  0.86466471676339  200.000%  1 in 7.4
 5  0.95021293163214  300.000%  1 in 20.1
 6  0.98168436111127  400.000%  1 in 54.6
 7  0.99326205300091  500.000%  1 in 148.4
 8  0.99752124782333  600.000%  1 in 403.4
 9  0.99872735771441  666.666%  1 in 785.8
10  0.99908811803445  700.000%  1 in 1096.6
11  0.99966453737210  800.000%  1 in 2981.0
12  0.99987659019591  900.000%  1 in 8103.1

What line 2 says, is that we expect, on average, 1 in 2.7 blocks, to be over 100%
What line 5 says, is that we expect, on average, 1 in 20.1 blocks, to be over 300%
etc.

It's something that a lot of people don't realise about the expected results when finding blocks

Just thought I'd post it again for the newer members

Kano,
What is the relationship between Pool Hash Rate, Diff and Probabilities, if any? Meaning as Diff Increases without Pool Hash Increase, how does that affect our Probabilities? I am thinking it only affects time to 100% Diff, your thoughts.
Thanks -Mine On 

Pool Hash Rate has no expected effect on Luck.

[Waztim]

Thank you

[kano]

On another note kano, on the invalid screen for workers, I understand what all of the acronyms but the "Hi" I don't know....I only get that on my S7 which isn't perfectly set up.

Anyone else can answer too.  


Stale, Duplidate "Hi" Rejected.

Difficulty has 2 ways to look at it.

The Network Difficulty value increases as it gets harder to find a block.
However, that is to simplify what it really is, and make it easier for people to understand it.

A block hash (498508) looks like this:
0000 0000 0000 0000 001c711eaa8898f83d737d5941a1c13a3bc0822a84906f0e
The required difficulty is 0x1800b0ed = 1,590,896,927,258.1 = 1.59*10^12

Out first ever block (325306) looks like this:
0000 0000 0000 0000 0c061098cb88b86cd48b9e7a6644c4ec26af471dcc779be4
It has fewer zeros, thus it is a larger number
The network difficulty was 0x181f6973 = 3,500,2482,026.1 = 3.50*10^9
A much smaller number, yet the block hash is a larger number.

So what all this means is, if you return a share with a difficulty that isn't good enough, it's actually "High" not "Low"
So under "Invalids" it says "Hi" - these are shares that should not have been sent since they didn't meet the difficulty requirements.
Although their difficulty 'number' was below the difficulty required by the pool, their difficulty value was "High".
e.g. if the pool says to send share with difficulty 8192 but you send lots of shares with difficulty 512, they will of course be rejected, but in the stats, listed under "Hi"

[VRobb]

On another note kano, on the invalid screen for workers, I understand what all of the acronyms but the "Hi" I don't know....I only get that on my S7 which isn't perfectly set up.

Anyone else can answer too.  


Stale, Duplidate "Hi" Rejected.

Difficulty has 2 ways to look at it.

The Network Difficulty value increases as it gets harder to find a block.
However, that is to simplify what it really is, and make it easier for people to understand it.

A block hash (498508) looks like this:
0000 0000 0000 0000 001c711eaa8898f83d737d5941a1c13a3bc0822a84906f0e
The required difficulty is 0x1800b0ed = 1,590,896,927,258.1 = 1.59*10^12

Out first ever block (325306) looks like this:
0000 0000 0000 0000 0c061098cb88b86cd48b9e7a6644c4ec26af471dcc779be4
It has fewer zeros, thus it is a larger number
The network difficulty was 0x181f6973 = 3,500,2482,026.1 = 3.50*10^9
A much smaller number, yet the block hash is a larger number.

So what all this means is, if you return a share with a difficulty that isn't good enough, it's actually "High" not "Low"
So under "Invalids" it says "Hi" - these are shares that should not have been sent since they didn't meet the difficulty requirements.
Although their difficulty 'number' was below the difficulty required by the pool, their difficulty value was "High".
e.g. if the pool says to send share with difficulty 8192 but you send lots of shares with difficulty 512, they will of course be rejected, but in the stats, listed under "Hi"

And THAT'S why so many of us kanopool faithful mine here with no thoughts of leaving. You are our sensei, kanosan. 
Mine on! 

[clgrissom3]

Amen to that

[Waztim]

I am witnessing a 1200 BTC Block of shares being sold on GDAX at $17,250. WOW!! $20+ Million dollars.

[2tights]

I am witnessing a 1200 BTC Block of shares being sold on GDAX at $17,250. WOW!! $20+ Million dollars.

someone just ejected the rocket in their gold plated escape pod.

[mdude77]

Hurray, looks like the pool passed the 30PH/s mark.

M

[fjtropepe]

I wonder if that was the miner I added a few hours ago... lol. She is purring.

[ChickenKillr]

What would be the reason that one would purchase this unit over the S9? Reliability is much better or so I have read, but power consumption is not. Would it be the fact that bitmain is not months behind and paying the scalper prices on ebay is absurd? Not trying to start anything here. Just attempting to confirm what I believe the reasons are based on my research. All in all given the retail pricing of both units wouldn't the S9 be the better machine 9 (not considering reliability).

Well with Bitmain where you have to pay 3 months in advance for an S9 ... that's 3 months of lost mining ... which is a VERY long time.

If instead you can get a miner much faster ... then that also needs to be factored in.

At the moment neither of them can supply miners quickly, but a few months back most people ignored the fact you could get an A7 when you couldn't get an S9.

We'll see what happens when the A8 is released ...

Then of course, as mentioned above, the RMA on an S9 is pretty much a joke ... so you gotta hope your S9 never fails ...

I ordered two S9 in the beginning of November and they arrived today. I was totally not prepared as everyone says two months out and even the details on the order page said it would be from the January lot. So now I am rush shipping power supplies to make use of miners that arrived over a month early.

how the heck, I ordered for the December 11-20th batch back in October and it still hasn't shipped. *sends angry email to Bitmain*