Author

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

xuy
member
Activity: 92
Merit: 10
I think your math is correct. Though probability has no memory, the chance of having 2 of 1 in 2000 so closely (within 4) is 1 out of million.
The question is with increased hash rate this pool gets more bad luck and is supposed to be less variance.
It will be great if we can find the issue. Otherwise we can just blame bad luck.


I remember some years ago when slush pool had a several month long streak with really bad luck, but as i remember it they found out it was some bug cousing it
.


This is maybe just bad luck but how big is the chance of getting 2 devilblocks so close to each other ? Or should I see it as every new block is a new block and what happened before doesnt matter at all ?

The first block was 1 in 2000

The second block is About 1 in 2000

But they were not back to back which would be a 1 in 4,000,000 chance.

My math skills to determine. The chance of two .9996 cdf blocks out of four are not up to the task.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Meanwhile, I've requested the big rentals to stop mining for the time being so the hash rate is back down to mostly just direct hardware now.
full member
Activity: 235
Merit: 100
I have also moved my miners for the time being, would love to return when everything is back to normal.
I can honestly say the last 2 months have been very steep roller coasters.
This problem didn't exist 3-4 months ago... has to be some bug somewhere!

SOME ONE GET THAT BUG SPRAY!!!! LETS GET THIS BUG OUT OF HERE!
full member
Activity: 228
Merit: 100
Mine ON!!!
I remember some years ago when slush pool had a several month long streak with really bad luck, but as i remember it they found out it was some bug cousing it
.
Yep. It was genesis mining running equipment that couldn't find blocks. After months of us all complaining about it and hearing nothing from slush, they finally kind sorta announced the problem and let them keep all the coin they stole. A GIANT F*** YOU to all the miners who had been loyal for years. That's when I found this pool.

Folks this happens every time there is a period of bad luck. Everybody comes out with their conspiracy theories. Yet nobody complains when we have months of phenomenal luck like last February and April.

At least here, you know that Kano is on it and provides you with regular updates. And if he does find something wrong, he tells it like it is no matter what the problem was.

definitely a plus
this is why i like this pool you actually got some to talk to and answer your questions
specilly when you are a noob
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I remember some years ago when slush pool had a several month long streak with really bad luck, but as i remember it they found out it was some bug cousing it
.


This is maybe just bad luck but how big is the chance of getting 2 devilblocks so close to each other ? Or should I see it as every new block is a new block and what happened before doesnt matter at all ?

The first block was 1 in 2000

The second block is About 1 in 2000

But they were not back to back which would be a 1 in 4,000,000 chance.

My math skills to determine. The chance of two .9996 cdf blocks out of four are not up to the task.

The fact that we had 2 good blocks between 2 devilblocks must change the "1 in 4000000" chance, but that´s above my pay-grade.
Yeah the problem is that you can't actually use the result of that calculation.
Statistics requires impartiality.

Selecting a range of data, specifically based on the results: the first and last being the worst possible values, invalidates the statistical analysis.

As you will see on the web site, there is no CDF[Erl] of data that defines a set of data based on the results of that data, since that isn't valid.
The boundaries are all unrelated to the results -> months, or a specific number of blocks.
newbie
Activity: 27
Merit: 0
Last chicken going to chopping block. The rooster! I’m all in.
member
Activity: 69
Merit: 10
cryptodonkey on the pool.
I remember some years ago when slush pool had a several month long streak with really bad luck, but as i remember it they found out it was some bug cousing it
.


This is maybe just bad luck but how big is the chance of getting 2 devilblocks so close to each other ? Or should I see it as every new block is a new block and what happened before doesnt matter at all ?

The first block was 1 in 2000

The second block is About 1 in 2000

But they were not back to back which would be a 1 in 4,000,000 chance.

My math skills to determine. The chance of two .9996 cdf blocks out of four are not up to the task.

The fact that we had 2 good blocks between 2 devilblocks must change the "1 in 4000000" chance, but that´s above my pay-grade.
member
Activity: 69
Merit: 10
cryptodonkey on the pool.
I remember some years ago when slush pool had a several month long streak with really bad luck, but as i remember it they found out it was some bug cousing it
.


This is maybe just bad luck but how big is the chance of getting 2 devilblocks so close to each other ? Or should I see it as every new block is a new block and what happened before doesnt matter at all ?
full member
Activity: 658
Merit: 118
Just for fun, I pointed all my other miners here too -only a couple dozen TH, but I hope it brings some luck (and I love its lower fees than other pools.)
member
Activity: 658
Merit: 21
4 s9's 2 821's
Well, just in case anyone gets upset about me not posting, here's a post Tongue

I know enough of the (non-rental) pool hash rate to know it's not a miner causing it, and I'm also looking into this from a few angles to make sure everything is running correctly.

With half the hash rate rental and the other half miners, and the fact that we broke the last long block with a rental, it does leave it all in the realms of the most likely answer being that it is simply just bad luck.
There's been no changes to the mining part of the pool code since I added the 🐈 to the coinbase (and only one massive change before that in the past year to include segwit and fix a 100% crash condition in the code)
I did of course (in both cases) test the code and make sure it did produce valid blocks, so unless there's some bug hiding there in the mining part of the code for months of finding blocks, I can assume it's all OK on that front (though I am checking things on that front as well of course)

The majority of the big miners are still around and that's what matters to keep the pool hash rate up, so anyone with theories about me causing it, that I've seen posted ... well ... yeah I'm not sure why I'd want the pool, that I've spent more than 3 years connected to it 24/7 every single day (except when some damn planes don't have working satellite wifi), to crash and burn ... ... ...

Let's hope things change for the better kano-san! 
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Well, just in case anyone gets upset about me not posting, here's a post Tongue

I know enough of the (non-rental) pool hash rate to know it's not a miner causing it, and I'm also looking into this from a few angles to make sure everything is running correctly.

With half the hash rate rental and the other half miners, and the fact that we broke the last long block with a rental, it does leave it all in the realms of the most likely answer being that it is simply just bad luck.
There's been no changes to the mining part of the pool code since I added the 🐈 to the coinbase (and only one massive change before that in the past year to include segwit and fix a 100% crash condition in the code)
I did of course (in both cases) test the code and make sure it did produce valid blocks, so unless there's some bug hiding there in the mining part of the code for months of finding blocks, I can assume it's all OK on that front (though I am checking things on that front as well of course)

The majority of the big miners are still around and that's what matters to keep the pool hash rate up, so anyone with theories about me causing it, that I've seen posted ... well ... yeah I'm not sure why I'd want the pool, that I've spent more than 3 years connected to it 24/7 every single day (except when some damn planes don't have working satellite wifi), to crash and burn ... ... ...
xuy
member
Activity: 92
Merit: 10
A big factor is difficulty. But it seems that more hashrate didn't bring good luck or less variance, especially with 2 very bad luck (~800%) out of 5. Some bigger pools (found at https://btc.com/) seem to have less variance in luck even within last 3 days. It seems less hashrate had less variance for this pool.

From my observation our luck got really good when some miners had to shut down for the hurricane. It also got really good when Labrador had some electricity issues a few weeks back and was offline. I don't know anything about code, but could to much hashrate cause it not to be efficient? You threw a ton of hashrate at it and only got 3 blocks for the effort. I know a year makes a big difference, but 70 blocks at 33.55Phs last November. Math is not adding up, so lets think outside the box.
newbie
Activity: 47
Merit: 0
You threw a ton of hashrate at it and only got 3 blocks for the effort.

Other pools did also grown 10% ~ 20% extra hashrate within last 2 weeks
newbie
Activity: 39
Merit: 0
We are on page 1492. Columbus stumbled across America. Hell we should be able to find block.  Grin
newbie
Activity: 39
Merit: 0
From my observation our luck got really good when some miners had to shut down for the hurricane. It also got really good when Labrador had some electricity issues a few weeks back and was offline. I don't know anything about code, but could to much hashrate cause it not to be efficient? You threw a ton of hashrate at it and only got 3 blocks for the effort. I know a year makes a big difference, but 70 blocks at 33.55Phs last November. Math is not adding up, so lets think outside the box.
legendary
Activity: 952
Merit: 1003
Question @kano:
Is the blockfinding in any way connected to the core client?
The only thing changed in the last few weeks is core update to 15.x. Isn't this right?
Okay beside the split.

Sorry for this unqualified Question. This just came to my mind cause I updated my node to 15.0.1.


Come ON BLOCKS!!!!
I'll answer that...no, Core doesn't affect finding blocks. It's your wallet, or if you're running a full node, you're helping process the mempool (the way I understand it). That's not mining.

Anyway...I've been running a full node for a long time, and have been running 15.0.1 with no issues.

Mine on!
newbie
Activity: 27
Merit: 0
just sacrificed a chicken...................BTC

Are you JoeBu?

If no block found in one hour another chicken gets sacrificed!..................BTC

Another dead chicken.  I have only two left and the wife is getting pissed I'm killing all our chickens!   One more chicken boys......
newbie
Activity: 47
Merit: 0
I'm out...
So sorry, but it's way too red here.
I'm no hopper, but what we need here is ? yes luck!
Wish all of you here: be on the lucky side of life/pool Wink
member
Activity: 658
Merit: 21
4 s9's 2 821's
Looks like we got paid for the last three blocks though within the past 24 hours, that's good to see. 
legendary
Activity: 1540
Merit: 1001
Not really tiny in first place.
But he also has to pay all the serverhosting,
fibre connections for low latencies etc.

Granted.  Also, on average, it's supposed to be more than one block found a day too.

M
Jump to: