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

[kano]

I'm about to do a ckdb restart - this of course means it doesn't affect the miner connection at all - just the web site.
Changes are:
1) Remove everyone's 2FA who was testing and show the 2FA menu for everyone to be able to enable 2FA if they want
2) Add worker name matching to the shift graph as requested
3) Add a tick box for each worker on the worker graph to temporarily turn worker lines on and off to make it easy to see overlapped lines

About 2FA:
To enable 2FA is a 2 step process described on the new 2FA menu page:
1) Click on the "Setup" button to generate a secret key
2) Successfully "Test" using 2FA
Until you succeed doing 2) it wont be enabled.
Once it is enabled, you cannot disable it without using 2FA.

The 2FA test screen shows your secret key, but you cannot ever see it again once the 2FA test is successful.
You need to securely store the secret key somewhere to be able to setup another authentication app after 2FA has been enabled.
e.g. if you lose/destroy your 2FA device you will need the secret key to setup another device.
The other settings (stated on the test page) are currently the same for everyone and aren't secret in any way.

You will receive an email when you click on "Setup" and again when you successfully test/enable 2FA.
The email messages do not contain the 2FA secret key or other settings information.

Edit: completed.

[1714763595]

1714763595

[1714763595]

1714763595

[1714763595]

1714763595

[1714763595]

1714763595

[1714763595]

1714763595

[1714763595]

1714763595

[LoneRangir]

So there will be a point in the (near?) future where the pool goes BIP101 (non-XT)?  There's software available to do that?  The sig change implies we're heading that way?

No, the sig change implies we are voting for BIP 100 instead of BIP 101. The two are mutually exclusive choices, but it's a very simple switch. If the sky falls, pigs fly, dolphins start talking English, and BIP 101 gains a majority in 2016, then sure we'll switch to BIP 101.

Okay, I wrote the wrong term in my message.  After reveiwing, it should have been BIP100.  After googling around a bit, I found a summary here.  Sorry for the confusion in my question.  Need to research more....

http://themerkle.com/news/current-state-of-the-blocksize-debate-bip-100-vs-bip-101/

[CapnBDL]

So there will be a point in the (near?) future where the pool goes BIP101 (non-XT)?  There's software available to do that?  The sig change implies we're heading that way?

No, the sig change implies we are voting for BIP 100 instead of BIP 101. The two are mutually exclusive choices, but it's a very simple switch. If the sky falls, pigs fly, dolphins start talking English, and BIP 101 gains a majority in 2016, then sure we'll switch to BIP 101.

ck...can the Dolphins spreak Spanish?

I won't be going 'X' until it's mandatory!


 

[aarons6]

Edit: You can now get a email notification if an individual worker does not submit a share in over 5 minutes.

its working great. one issue tho.
i moved a worker to solo pool for a few days, and now it wont stop emailing me.. lol..
maybe make a check box of the workers so i can check the workers i want to monitor?

[CapnBDL]

@ kano or ck,

Which was the last version of CGminer to support the Zeus Blizzard & Gridseed Blade scrypt miners?


Thanks

[kano]

@ kano or ck,

Which was the last version of CGminer to support the Zeus Blizzard & Gridseed Blade scrypt miners?

Thanks

None, official cgminer has no altcoin support at all.
Only forks do that.
Scrypt support was removed long, long ago.
Gridseed was never supported.

[CapnBDL]

@ kano or ck,

Which was the last version of CGminer to support the Zeus Blizzard & Gridseed Blade scrypt miners?

Thanks

None, official cgminer has no altcoin support at all.
Only forks do that.
Scrypt support was removed long, long ago.
Gridseed was never supported.

I must be using a fork of cgminer then. I'm running 4.3.5 currently but I think there is a newer one. Can't seem to find it in git. OK..well, thanks anyway. I'll just keep looking.

[WBF1]

Block!

[wlefever]

Block!

Glad to find it, but i'm ready for some of that bright green luck again!

[WBF1]

Block!

Glad to find it, but i'm ready for some of that bright green luck again!

Ditto

[ZACHM]

Edit: You can now get a email notification if an individual worker does not submit a share in over 5 minutes.

its working great. one issue tho.
i moved a worker to solo pool for a few days, and now it wont stop emailing me.. lol..
maybe make a check box of the workers so i can check the workers i want to monitor?

I might be able to get that to work eventually, but for a quick fix I set it so it will only notify you every 5 minutes for 1 hour. After that you will not get the notification anymore.

[scotty2u2]

Just curious...

I let the pool adjust my worker diffs. Sometimes the diff gets adjusted to values less than the pool minimum, and usually on only one miner, sometimes two. I have one S4 and four S5s running, and it seems that only one of the S5s is affected most of the time.

If I restart the affected miner, it starts over at the pool's 1.042k, and sometimes I need to do a hard restart.

Is this normal, or is it likely that there's a problem with that S5? Does this happen to anybody else?

 

[CapnBDL]

Just curious...

I let the pool adjust my worker diffs. Sometimes the diff gets adjusted to values less than the pool minimum, and usually on only one miner, sometimes two. I have one S4 and four S5s running, and it seems that only one of the S5s is affected most of the time.

If I restart the affected miner, it starts over at the pool's 1.042k, and sometimes I need to do a hard restart.

Is this normal, or is it likely that there's a problem with that S5? Does this happen to anybody else?

 

I don't know much about the S5s but I am pretty sure the pool min is diff 42. No way you run that slow.

[VirosaGITS]

Just curious...

I let the pool adjust my worker diffs. Sometimes the diff gets adjusted to values less than the pool minimum, and usually on only one miner, sometimes two. I have one S4 and four S5s running, and it seems that only one of the S5s is affected most of the time.

If I restart the affected miner, it starts over at the pool's 1.042k, and sometimes I need to do a hard restart.

Is this normal, or is it likely that there's a problem with that S5? Does this happen to anybody else?

 

I don't know much about the S5s but I am pretty sure the pool min is diff 42. No way you run that slow.

Not unless you somehow don't notice when your S5 start hashing at 1gh xD.
You didnt mention the most important, scotty2u2. Whats your accepted hashrate for that unit on Kanopool?

[Mikestang]

Sometimes the diff gets adjusted to values less than the pool minimum

That's not possible.  It's a minimum value (42) because, by definition, that's as low as the pool will go.

What specific values are your machines adjusting down to?  If your shares are getting accepted then there's no issue here I can see.

[scotty2u2]

Sorry guys...

Under Worker Management, I have the minimum diff for all workers set to zero. The values I was referring to are the ones listed under 'Work Diff' on the Workers page.

 

http://i574.photobucket.com/albums/ss187/scottyonbass/diff_zpsejxdeotf.jpg

[kano]

Yeah the pool minimum is 42, so it can go down below 1042 if your device is around 1.4TH/s or less.
The pool tries to keep it static so it shouldn't change much, but the target is 18 shares per second minute. (Edit: oops )
The value it uses of course wont affect your average payout.
If you have a value you want it to stay above, use the Workers->Management page to set it there.

Edit: just did a pool restart to add in a small bugfix for ckpool.
Was an immediate restart so few if any miners should have failed over.

[aarons6]

Edit: You can now get a email notification if an individual worker does not submit a share in over 5 minutes.

its working great. one issue tho.
i moved a worker to solo pool for a few days, and now it wont stop emailing me.. lol..
maybe make a check box of the workers so i can check the workers i want to monitor?

I might be able to get that to work eventually, but for a quick fix I set it so it will only notify you every 5 minutes for 1 hour. After that you will not get the notification anymore.

That will work. You can even make it email every 30 minutes twice if the worker doesn't send a share for 5 minute. Once you get the email you go check the miner when you can.

[scotty2u2]

Thank you everybody, for all your responses. You guys are great!   

[BitcoinNewsMagazine]

I just restarted the pool to change the sig.
There should have been little if any failover since it was a normal immediate restart.

I've changed the sig to now say "/Kano /BIP100/"

I see BIP100 as the best option in all this crap that's been going on recently since it gives block size control (up to 32MB) to the pools/miners.

I see XP-BIP101 giving control to Herne/Gavin without even proper consensus - so I'm am clearly stating I'm against XT-BIP101

The sig change itself is not following any officially defined voting anywhere and since it is a sig change only it is not changing the blocks produced either.

Are you using coinbase to show your preference for BIP 100 per https://bitcointalk.org/index.php?topic=789369.4440



Thanks for supporting BIP 100.