Mining for more than 2 weeks with only 2 blocks found.
Actually this was the first time that I joined a small pool
I have you now as my second pool...
good luck with your projects will come back soon
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2221. (Read 5352295 times)
December 01, 2014, 04:14:35 AM
November 30, 2014, 02:01:31 PM
I think I have come to the conclusion that I must bring bad luck to this pool? 
I gave up can't deal with it anymore. Maybe next month I will come back.
I noticed you were gone. I only have 1 miner pointed here and plan on staying this time. I left last time before a block was found and just gave up any payment I had earned.
yeah I caught most of the good luck blocks. Missed some of them. But I did catch all the bad luck blocks. When I get some more hash I will point something here. ( purchased 2x sp20's). So maybe tues or weds I will point gear back here.
November 30, 2014, 12:17:39 PM
I think I have come to the conclusion that I must bring bad luck to this pool?
I gave up can't deal with it anymore. Maybe next month I will come back.
I noticed you were gone. I only have 1 miner pointed here and plan on staying this time. I left last time before a block was found and just gave up any payment I had earned.
November 30, 2014, 11:26:11 AM
I think I have come to the conclusion that I must bring bad luck to this pool?
I gave up can't deal with it anymore. Maybe next month I will come back.
November 30, 2014, 11:08:59 AM
Well, anyone looking at the CDF, that 0.98 means that all pools should average one block like that or longer in every ~50 blocks.
That being the pool's 25th successful block, means it's not at all unexpected.
But at least the average since the pool started is still looking pretty good
69.52% of diff average per block.
i.e. we've found ~1.44 times the number of expected blocks so far.
A long block like that indeed affected those two numbers as I said in that post on the previous page, but that luck streak before has kept the average better than expected.
Of course if you start mining at any time, the expected long term average is 100%, but the shorter term average will of course vary a lot more.
That all being said, the one thing that makes that guaranteed variance easier to bear with PPLNS, is the higher pool hash rate.
We are slowly climbing up there, but of course the more hash rate the better
1700TH means at the moment an expected average block time of ~1day 4.25hrs so it's getting better
That being the pool's 25th successful block, means it's not at all unexpected.
But at least the average since the pool started is still looking pretty good
69.52% of diff average per block.
i.e. we've found ~1.44 times the number of expected blocks so far.
A long block like that indeed affected those two numbers as I said in that post on the previous page, but that luck streak before has kept the average better than expected.
Of course if you start mining at any time, the expected long term average is 100%, but the shorter term average will of course vary a lot more.
That all being said, the one thing that makes that guaranteed variance easier to bear with PPLNS, is the higher pool hash rate.
We are slowly climbing up there, but of course the more hash rate the better
1700TH means at the moment an expected average block time of ~1day 4.25hrs so it's getting better
But it looks like your standard deviation is over 101%. How has your variance been trending with time???
November 30, 2014, 08:48:49 AM
I think I have come to the conclusion that I must bring bad luck to this pool?
November 27, 2014, 06:26:01 PM
Con,
There is a file descriptor leak in gen_loop(proc_instance_t *pi) probably in other loop places also
Some jumps to reconnect do not close sockd.
The quick fix for me is
reconnect:
if (si) {
kill_server(si);
reconnecting = true;
// close checks for -1
Close(sockd);
}
Thanks Ioshia. Fixed in master and the development branch (userstats). There is a file descriptor leak in gen_loop(proc_instance_t *pi) probably in other loop places also
Some jumps to reconnect do not close sockd.
The quick fix for me is
reconnect:
if (si) {
kill_server(si);
reconnecting = true;
// close checks for -1
Close(sockd);
}
November 27, 2014, 02:36:49 PM
Con,
There is a file descriptor leak in gen_loop(proc_instance_t *pi) probably in other loop places also
Some jumps to reconnect do not close sockd.
The quick fix for me is
reconnect:
if (si) {
kill_server(si);
reconnecting = true;
// close checks for -1
Close(sockd);
}
There is a file descriptor leak in gen_loop(proc_instance_t *pi) probably in other loop places also
Some jumps to reconnect do not close sockd.
The quick fix for me is
reconnect:
if (si) {
kill_server(si);
reconnecting = true;
// close checks for -1
Close(sockd);
}
November 27, 2014, 01:09:10 AM
Doing another ckdb restart - as usual, shouldn't affect mining, but the web stats will be unavailable while I do it.
Quite a sizable change, so ... I thought I better warn when I did it (now) ...
Finished. Quite a sizable change, so ... I thought I better warn when I did it (now) ...
November 26, 2014, 11:24:25 PM
Me too, disregard pm question. Thanks.
November 26, 2014, 09:51:29 PM
Kano I also sent a question on lat payout when you have a chance.
Yes I've not done the payout for 331660 yet.Been working on code ... it matured 50 minutes ago ... will do it shortly.
Edit: and confirmed
got it thanks
November 26, 2014, 09:19:08 PM
Kano I also sent a question on lat payout when you have a chance.
Yes I've not done the payout for 331660 yet.Been working on code ... it matured 50 minutes ago ... will do it shortly.
Edit: and confirmed
November 26, 2014, 08:26:07 PM
Kano I also sent a question on lat payout when you have a chance.
November 26, 2014, 05:02:12 PM
Next block will found at: 2014-11-28 09:52:11
Well that gives your guess a 24 hour range since you didn't specify a timezone, so it could be quite possible 
That's still a pretty specific guess. 60 seconds per minute, 60 minutes per hour, that's 1 out of 3600.
Assuming I did my math right...
M
November 26, 2014, 04:52:34 PM
Next block will found at: 2014-11-28 09:52:11
Well that gives your guess a 24 hour range since you didn't specify a timezone, so it could be quite possible November 26, 2014, 03:55:07 PM
Block 331574 payout sent out
Visible at the usual blockchain link:
https://blockchain.info/address/1KzFJddTvK9TQWsmWFKYJ9fRx9QeSATyrT
Visible at the usual blockchain link:
https://blockchain.info/address/1KzFJddTvK9TQWsmWFKYJ9fRx9QeSATyrT
PM sent about the payout
November 26, 2014, 03:17:05 PM
Next block will found at: 2014-11-28 09:52:11
November 26, 2014, 02:32:31 PM
Nice! Payout was a little more than I expected and we found another block. It is a good day my friends! 
Same here regarding the payout comment. ck and kano- thank you!!! 
November 26, 2014, 01:23:08 PM
Nice! Payout was a little more than I expected and we found another block. It is a good day my friends!
November 26, 2014, 09:12:09 AM
Block 331574 payout sent out
Visible at the usual blockchain link:
https://blockchain.info/address/1KzFJddTvK9TQWsmWFKYJ9fRx9QeSATyrT
Visible at the usual blockchain link:
https://blockchain.info/address/1KzFJddTvK9TQWsmWFKYJ9fRx9QeSATyrT
oh yisss 55c/0.00148031 BTC to me!
Jump to: