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

Dang....followed the directions to install the rewrite for cgminer (s3) but it says I'm still using 4.6.1-1. This can't be right & I see no difference in web interface. Knew this was gonna give me trouble....What did I do wrong?? I am not any good /w Linux...need some help plz. Thank You

Still won't have all my little r-Box110 miners on-line due to that lightning loss explained in previous post, but they will have to wait for funding. I'm lookin' to grab another s3 along the way too. Love these things.

OK....ppl are very happy /w the updated s3 software so it's time I got adventurous........now where did I put my 'putty' knife?


Thanks for the work!! You are the best.

Payout 363848 sent
68532dcb601ae2653940638b4fec3c3c601837059c9773d1a986985a00147282
and confirmed

Great thanks - will try it then.

Will point a few S3's at your pool soon and test it for a week.

Cheers

looks like we have ourselves a new shark in the pool..
"bitclub" has almost half the pool hash..

hopefully he will help us find a few more blocks..

(BTC + Txn) less 0.9% fee
https://kano.is/index.php?k=payout
The Bocks and Help menu on the Web site are accessible to anyone even if they don't login.

My S3 update can't brick your S3 - that's why I did it that way.
Yes flashing the S3 can (in rare circumstances) brick the miner, but my smaller file update avoids that completely.

@ Kano - whats the fee at your pool kano.is - can't see that mentioned after I joined up?

you are doing some great works here - esp the S3 mods

Might try them out if I can get Putty to work for me to mod the miners - tried Putty before and failed and I hate bricks.

Many thanks - usukan

It does not change anything in the settings, but earlier it was more stable.

Better hardware.
Some miners are slow to send out work or send out bad, high or duplicate work.
Also if you have poor connectivity to the pool you may get higher rejects.
Though those values don't look bad ...
I was just about to check your workers on the web site ... but we just found a block and it resets the counters
Check the workers page again in a few hours - it shows the overall % Invalid for each of your workers for the current block.

What that edit to get rid of "Inv Diff", change difficult?

If you mean the "0"s in there you want zeros.
They are (as it says at the top) "Inv Diff" - invalids - so the lower it is the better of course - 0 being the best.
They are stale, duplicate, hi and rejected shares (difficulty)
https://bitbucket.org/ckolivas/ckpool/commits/b1be1edd8b761859416315da673d33643f8cd8aa?at=master

Anyone who noticed (probably no one?) I restarted the pool so should just be a reconnect message
Pool's been running smoothly for a week so I threw in a restart.

4uhfj tenshi     2015-07-05 00:38:42+00   45m 1s   3.280M          0   5.22THs   591   5,549.70
4uha9 sena    2015-07-04 23:57:43+00   41m 0s   2.956M   40.960k   5.16THs   503   5,877.31
4uh5f rika           2015-07-04 23:17:42+00   40m 1s   3.024M   1.024k   5.41THs   529   5,716.20
4ugyr quinn           2015-07-04 22:32:12+00   45m 30s   3.437M   8.192k   5.41THs   612   5,615.27
4ugte paru           2015-07-04 21:52:12+00   40m 0s   2.936M   16.384k   5.25THs   509   5,767.80
4ugoq origami    2015-07-04 21:22:12+00   30m 0s   2.092M          0   4.99THs   360   5,811.20
4ugk8 nodoka   2015-07-04 20:41:11+00   41m 1s   2.966M          0   5.18THs   529   5,605.87
4ugef mutsumi   2015-07-04 20:01:15+00   39m 57s   3.462M   49.152k   6.20THs   587   5,898.03

Why zero? The calculate before all shares...

Right, but that would also mean that their monitoring tool wouldn't work on other mining devices either ... which would seem to be a silly restriction to make.
I wrote the API, version controlled it, made sure it was backwards compatible (i.e. no changes to break old code that used it properly)
... so yeah making a monitor that doesn't support the standard API seems a bit silly

... though I did break it once when I removed CPU/GPU support - but no effect on non CPU/GPU mining

New S3 cgminer is a good to go .....
@Kano - yes some miner monitors only worked well with the bitmain forked API ..... but by any measure, its the only one that's been around for bitmain gear for forever, so not unexpected.

Go ahead?

Well someone is already running a farm with about 2000 of them with the updated version
Although you won't see any big jump in performance, the gains are of course:
1) Removal of all the Bitmain code problems, since it's master cgminer, not their problematic forked code
2) Clear noticeable CPU usage/load drop - this also means a much lower chance of work processing delays getting work back to the pool
3) Updated to latest cgminer 4.9.2
4) Allow web to show and modify the API access settings
5) Web field to add any other cgminer option if you want e.g. to solo mine to your own bitcoind
6) Updated web stats page - I got rid of a lot of useless information and also prioritised more important numbers and added a couple

However, it would seem that some people who write monitoring tools may have not allowed the standard cgminer API, but only assume that the AntS3 will put out the non compatible Bitmain API results - so you'll have to check with whoever wrote whatever monitoring tool you use and make sure they didn't do that.
There's no reason why they would do that, they can supports both easily, but the important point is to always allow the standard cgminer API so you know it will work with any miner that adheres to the standard and then can add hacks in for devices that break that if needed

Kano's s3 software working just fine on my s3s and very easy to install.

Study long study wrong

     Damn...lost a power supply today to lightning. It'll be a while before I can replace it due to finances.        I see BitClub is more than making up for my little lost hash tho.       Still waiting on the 'Go Ahead' before trying to install the updated s3 software.

However He just found us a block while I was doing the payout (coz I woke up not long ago)

Payout 363724 sent
0af2584bd376ce1b1a049f4af0322765127726482d31e76f9e5466f550cda515
(not confirmed yet)

Looks like the pools hash rate has nearly doubled in the last 12hrs. Not sure if it will be a blessing or a one hitter quitter