Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1802. (Read 5352322 times)

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
The real problem with unlucky long blocks is... they take long. I know that sounds silly to say but that's why they're perceived as prolonged stretches of bad luck whereas they're still only one solved block. If you don't look at the duration of blocks and you just line them up as Long or Short and list them, the last 10 blocks on kano.is are: SSSLSLSSSL

Anyway the L is fucking fucked UP!!!
That, I cannot disagree with  Tongue
full member
Activity: 162
Merit: 100
The real problem with unlucky long blocks is... they take long. I know that sounds silly to say but that's why they're perceived as prolonged stretches of bad luck whereas they're still only one solved block. If you don't look at the duration of blocks and you just line them up as Long or Short and list them, the last 10 blocks on kano.is are: SSSLSLSSSL

Anyway the L is fucking fucked UP!!!
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
The real problem with unlucky long blocks is... they take long. I know that sounds silly to say but that's why they're perceived as prolonged stretches of bad luck whereas they're still only one solved block. If you don't look at the duration of blocks and you just line them up as Long or Short and list them, the last 10 blocks on kano.is are: SSSLSLSSSL
hero member
Activity: 777
Merit: 1003
When we had our 666.666% block the pool was only at 2.27PHs.  Wink
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hashing power goes up, we find fewer blocks and get paid less for each???

I've seen this happen many times even though it doesn't make any sense???

As we all know, with more hashing power we should find blocks quicker and overall get the same payout - just more smaller payouts - less variance.

I'm not accusing the pool operators of anything wrong and believe this is a very good and honest pool.

Just "a feeling" based on something I noticed several times at slush and now noticing here, that's why I wasn't that crazy about this pool getting bigger.

No. Your perception is just skewed. It's only explained on this thread every second page what the probability is of these long blocks. Look at the long term statistics on this pool - there is no inexplicably prolonged bad luck.
sr. member
Activity: 442
Merit: 250
Found Lost beach - quiet now
Hashing power goes up, we find fewer blocks and get paid less for each???

I've seen this happen many times even though it doesn't make any sense???

As we all know, with more hashing power we should find blocks quicker and overall get the same payout - just more smaller payouts - less variance.

I'm not accusing the pool operators of anything wrong and believe this is a very good and honest pool.

Just "a feeling" based on something I noticed several times at slush and now noticing here, that's why I wasn't that crazy about this pool getting bigger.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Network hashrate is

771.886 PH/S

We should be getting something at pool rate 11ph

Big snow storm ready to hit the easy coast. Maybe that will influence things, power outages , network outages, etc.

haven't been around bitcoin long enough:
an odd scenario, but if difficultly manages to drop can mining pools resubmit previously close shares?
No. Block solves MUST be based on the previous block exactly. That's the basis for blockchain security.
hero member
Activity: 777
Merit: 1003
haven't been around bitcoin long enough:
an odd scenario, but if difficultly manages to drop can mining pools resubmit previously close shares?

No, there would most likely be several pools that had share higher than the new difficulty. Who's would be the right one?
vh
hero member
Activity: 699
Merit: 666
Network hashrate is

771.886 PH/S

We should be getting something at pool rate 11ph

Big snow storm ready to hit the easy coast. Maybe that will influence things, power outages , network outages, etc.

haven't been around bitcoin long enough:
an odd scenario, but if difficultly manages to drop can mining pools resubmit previously close shares?
legendary
Activity: 1274
Merit: 1000
Installed the pool Android app, configured it with my API, set the block found notification to on, and save it.
Then got a block found alert, thought to myself, its this real? Well, it could be a coincidence...
...but nahhh it was a software bug or something! :p


Same happened to me when I installed it. Apparently when you first time run it, it alerts for the last block found.

It also sends out a block found notice when the pool gets reset and stuff, you have to look at the date/time on the app of the last block found to be sure it's really a block. Smiley
hero member
Activity: 770
Merit: 523
Network hashrate is

771.886 PH/S

We should be getting something at pool rate 11ph

Big snow storm ready to hit the easy coast. Maybe that will influence things, power outages , network outages, etc.
legendary
Activity: 1302
Merit: 1001
42 hours+..... Always the worse hangovers after the best parties.  Embarrassed
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I have the DE node up and running again since yesterday.

All is running fine on it so far (touch wood) and the DNS for anyone who connects or reconnects to de.kano.is points back to it.

--

Anyone wanting a probability number for 350% we just went past:
Code:
0.96980261657768  350.000%  1 in 33.1
Yep on any pool you expect about one in 33 blocks to be 350% or more.
kano-san, I love this geeky math stat stuff!  Got a question, does the chance of finding a block at a given % of hash follow a normal distribution, or is it based of a different distribution curve.  i.e. if we have a 1:33.1 chance of finding a block of 350% or higher does that equate to the opposite end of the curve, such that we also have a 1:33.1 chance of finding a block of (1/350%) 28.6% or lower?
Which we have, many times, on this pool btw!!  Grin
The calculation for CDF I use is 1 - e^(-ratio)
It's not to specify a point on the 'graph' but the summation of the possibilities above (or below) that point.
So no it wont be simple inverse of the % ratio.

As with your example, the CDF of 0.286 is:
Code:
0.24873738405311  28.600%  1 in 1.3
So 'most' Smiley blocks (about 3/4) are expected to be above 28.6%
The number, you can read from that, is 1-0.2487... or 75.1%

However, that also means that 24.9% (about 1/4) of blocks are expected to be under 28.6%
Checking our history, indeed the number is ... 122 out of 463 - a fraction better than expected but close.
(122 includes our first orphan coz we are discussing probabilities here, not reward calculations)
member
Activity: 92
Merit: 10
Hey Kano another 4.7TH is headed to the pool... Pointing my S7 that is currently going through customs to the pool when it arrives. Currently have both of my S3+'s on the pool. I'll be staying here.
hero member
Activity: 770
Merit: 523
Kano, thanks for the near miss stats. It really helps cope with the lack of blocks.
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
I have the DE node up and running again since yesterday.

All is running fine on it so far (touch wood) and the DNS for anyone who connects or reconnects to de.kano.is points back to it.

--

Anyone wanting a probability number for 350% we just went past:
Code:
0.96980261657768  350.000%  1 in 33.1
Yep on any pool you expect about one in 33 blocks to be 350% or more.
kano-san, I love this geeky math stat stuff!  Got a question, does the chance of finding a block at a given % of hash follow a normal distribution, or is it based of a different distribution curve.  i.e. if we have a 1:33.1 chance of finding a block of 350% or higher does that equate to the opposite end of the curve, such that we also have a 1:33.1 chance of finding a block of (1/350%) 28.6% or lower?
Which we have, many times, on this pool btw!!  Grin

hero member
Activity: 777
Merit: 1003
Well it has been about 102 blocks since our last one over 350% so I'd say we are doing pretty good.
We did have a close one 11 ago @ 336.852%
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I have the DE node up and running again since yesterday.

All is running fine on it so far (touch wood) and the DNS for anyone who connects or reconnects to de.kano.is points back to it.

--

Anyone wanting a probability number for 350% we just went past:
Code:
0.96980261657768  350.000%  1 in 33.1
Yep on any pool you expect about one in 33 blocks to be 350% or more.
legendary
Activity: 1260
Merit: 1006
Mine for a Bit
Jump to: