KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2438 blocks

[CapnBDL]

No... if you truly want to get rid of the entire overlay directory:

Code:

rm -rf /overlay

That'll wipe the entire thing out recursively and forcibly.  Unlike Windows, there's no recovering from that.  There is no recycle bin or trash can from which you can restore things.  It's gone.

The README tells you what to delete to remove the 'Kano' version and put it back to the Bitmain version ...
https://github.com/kanoi/cgminer-binaries/blob/master/AntS3/README#L106

To update from my earlier version, you do not need to delete anything - that's why I didn't say that in the README

kano,

I guess I got confused then when I read this line33 in the readme:

'Once you extract it, you should delete it to save space in /overlay/'

Sheesh...didn't mean to make a federal case of it. I'm leavin' stuff alone. I'm mining fine /w the update installed. Thanks for a great job.

[kano]

...
kano,

I guess I got confused then when I read this line33 in the readme:

'Once you extract it, you should delete it to save space in /overlay/'

Sheesh...didn't mean to make a federal case of it. I'm leavin' stuff alone. I'm mining fine /w the update installed. Thanks for a great job.

Yeah that's the explanation of
https://github.com/kanoi/cgminer-binaries/blob/master/AntS3/README#L15

You can stop at "Explanation:"
https://github.com/kanoi/cgminer-binaries/blob/master/AntS3/README#L39

I've just now add a comment in there before Explanation
https://github.com/kanoi/cgminer-binaries/blob/master/AntS3/README#L30

[mrquick]

Just updated my S3 again to the latest build and all went well. The instructions are easy to follow even for a noob using putty.
Thanks again kano. 

[sorry2xs]

block 

[sorry2xs]

glad i came back a few hours back

[mrquick]

Wooohaaa.
Well done to kotodama. Stats shows them at 240GHs. Am I missing something?

[xZork]

Nice kotodama!  What are you mining with?!

[mrquick]

Last block still showing +1 confirms after half an hour.
 Is that normal?

I was just curious how long it usually takes to get past the +1 confirms.

[LoneRangir]

kano you should update the thread title with our present approx hashrate.

So is this the "new norm"?

[kano]

Wooohaaa.
Well done to kotodama. Stats shows them at 240GHs. Am I missing something?

Yep kotodama's highest hash rate of the past 3 weeks has been around 240GHs
Way to go for the little miners!
Or do call that the minor miners

Last payout (for block 364084) finally confirmed 5.5hrs ago also - before we found the block.

[kano]

kano you should update the thread title with our present approx hashrate.

So is this the "new norm"?

Well it's stayed that way for a while now - lets hope it continues.

[bgibso01]

So Koto was showing 229GH.  Well done sir, well done!

[innerchaos]

Payout 363911 sent
ca6fc32e30bdd9ef542f7eb4225e729678b99b72ffe45fb6ad394fd535e527ec
and confirmed

Anyone who takes detailed notice of the payouts and blocks ...
My payout included my part of the 'donation'/'fee'
Yeah that coinbase sent the donation differently - I fixed it after that - no problems caused of course, but you probably would have seen it if you looked at the block coinbase transaction itself also.
ckdb knows the right amount to reward everyone based on the whole block, not the coinbase transaction breakdown.

did I misunderstand this... I took this as you the pool operator accidentally gave away any fees you should be entitled and therefore did not get paid for this ??

[kano]

Payout 363911 sent
ca6fc32e30bdd9ef542f7eb4225e729678b99b72ffe45fb6ad394fd535e527ec
and confirmed

Anyone who takes detailed notice of the payouts and blocks ...
My payout included my part of the 'donation'/'fee'
Yeah that coinbase sent the donation differently - I fixed it after that - no problems caused of course, but you probably would have seen it if you looked at the block coinbase transaction itself also.
ckdb knows the right amount to reward everyone based on the whole block, not the coinbase transaction breakdown.

did I misunderstand this... I took this as you the pool operator accidentally gave away any fees you should be entitled and therefore did not get paid for this ??

Yes, I guess you misunderstood then.

ckdb knows the right amount to reward everyone based on the whole block, not the coinbase transaction breakdown.

I was pointing it out for anyone who does actually look closely at the coinbase and payout transactions since the above explains why they are a bit different.
(it did actually give 1/5 of my part of the 'donation'/'fee' to -ck so there's no problem there)

[kano]

Quick message coz I'm working on it.

I've taken the pool down while I repair the bitcoinds that I run on it.
One has crashed and got corrupted, the other (backup) one is so bogged down with the network that everyone is mining stale work.
As soon as I've reparied and recovered the bitcoinds the pool will be back up.
I don't want people mining useless work.

All back and running and all good.

[hurricandave]

Mine have switched back to Kano.is

[kano]

Payout 364297 sent
4763791efdf8586832489218a42c210112970c25fb82eae8097cd75e0a6f25dd
(with 10x the fee I usually use)
and confirmed

[CapnBDL]

Payout 364297 sent (with 10x the fee I usually use) and confirmed

10x ?

[kano]

... and just after that block we just found ... all the bitclub hashes were moved off the pool.
So we're back down below 2PH

[tlhIlwI]

... and just after that block we just found ... all the bitclub hashes were moved off the pool.
So we're back down below 2PH

Is the pool stats page working correctly? bitclub is still showing up on that page, but stuck at 1306.76.

It is never fun when such large hash leaves the pool. The blocks come slower and it takes forever for the N range to expand so that the payment amounts catch up.