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

...
Would it be possible display the last 100 blocks on the Blocks page? right now onl the last 42 are displayed. Maybe there is a reason 42 are displayed.

Thanks,

Whoever stopped sacrificing the rubber chicken, please start again. No block in 61hours just plainly suxors! 

Any reason why the invalid share count went up by 10x?

One of the more ugly restarts in a while ... everyone will have failed over.
All up and running ok again.

Heh, the pool uptime has been 7 days ... the last 10 blocks all under 100%
But ... OK ... just restarted it anyway

I wasn't doing any mining, just troubleshooting slowdowns and 'website access denied' problems on a completely unrelated web sites. I've accidentally found that your has the same problem as the other ones. This could cause you (and your members) problems as the most common symptom was 'slowdown', not 'doesn't work anymore', depending on the firewall setup on the miner's end.

Yeah  that's fine. Although ck broke the pool with his update. We haven't had a block solve since.
Can we start the hourly restarts? Lol

Firstly the AntS3 README is here:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS3
One big change I've added since I merged in the S3 changes into master git is to reduce CPU usage.
You'll find the Load Average spends most of it's time under 1.0 - and that change is advantageous, not harmful.
I basically removed a major CPU waste, doing something unnecessary.

There are a bunch of issues with the bitmain fork of cgminer, which are not in the master cgminer of course.
They are actually listed in the S2 README:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS2
down at the initial release

Master cgminer doesn't have the Best Share of Diff setting problem either (they added that problem to some of their versions)
Also, of course, it's the latest cgminer 4.9.2 which means it has all the latest cgminer fixes

The update is not a flash change, just a few reasonably simple steps to extract an archive into the Ant
The archive file is simply a gzipped tar of the changes that are all effectively the source code except for the cgminer binary itself.

Thanks for clarifying. Updated the first one and about to update the second with no issues.

The web interface changes are listed in the AntS3 README, the most important one being you can see and modify the API allow settings to make it secure.

Since you have an S3+ make sure you check what your settings are in the Advanced Tab before you update and set/save them again after the update.
However it's easy to see what settings my version is running since I also display them at the bottom of the Miner Status web page

Hi Kano, since BTCGUILD closed down i have used a few pools but none that made me want to stick with them. I happened upon this thread and your attitude and honesty have won me over so i'm pointing my s3+'s at your pool and will keep them there. I see you have written some modifications for the s3 but i can't seem to find the all the information. Is there a thread that explains it fully? Are there any performance gains or is it mainly a graphical change? Thanks in advance!

...

So whats the odds of keeping the luck at over 200% for the next 10 block with such a good luck streak over the last 10 block, or 25 and 50 for that matter.......

Payout 365602 sent
0469d434de8bfc6561e6eb9c440e8eb1885d5a38b3b779ff6b646e6e4615a5a1
and confirmed

So whats the odds of keeping the luck at over 200% for the next 10 block with such a good luck streak over the last 10 block, or 25 and 50 for that matter.......

Well ... actually ... it is valid to say it affects the % luck of the pool.

There is a problem in the bitcoin world of saying what the pool's luck is.

Although you would statistically expect that over a long period of time, the pool's accepted hashes would approach the expected: 100% luck, that isn't completely true.

There are factors that reduce the number of blocks found.
Specifically orphans.
Some pools have long term bad luck because they are slow at handling block changes and lose more blocks because of that.
Eligius is an example of this

There were also pools that counted stale shares for a short period of time after the block change had occurred.
While this makes the pool look better by lowering and lying about their reject statistics, it also has the long term effect of lowering the pool luck.
Not sure which pools do this.

One pool in particular doesn't count all the hashes used to produce it's blocks and thus reports luck higher than it really is.
P2Pool

The change does have a long term affect on our % luck, but it doesn't affect what is really 'Luck' - which isn't exactly what pools report

However, it is also true to simply say that running ckpool has a long term effect on the % luck since it handles block changes very fast.