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

[bctmke]

@ZachM I love your pool monitor the emails notifying of a block find are great.

[1714002927]

1714002927

[1714002927]

1714002927

[1714002927]

1714002927

[ZACHM]

@ZachM I love your pool monitor the emails notifying of a block find are great.

Thanks, glad you like it.

[clgrissom3]

@ZachM I love your pool monitor the emails notifying of a block find are great.

Same here.  It also makes it easy to see how your miners are performing over time.  That came in real handy for me yesterday in pinpointing an issue with one of my older machines.

[PPOC]

And it goes on and on 

Bitcoin Difficulty:    93,448,670,796
Estimated Next Difficulty:    108,641,439,562 (+16.26%)
Adjust time:    After 2013 Blocks, About 14.1 days

1st 2-3 days are <usually> way off on the forecast, if it does not come down by Monday, then yea big trouble.....

[Real-Duke]

Ok thanks for your explain! Was never in the situation before that Im online when there is only 1 Block more to go before adjusting to new diff 

[kano]

And it goes on and on 

Bitcoin Difficulty:    93,448,670,796
Estimated Next Difficulty:    108,641,439,562 (+16.26%)
Adjust time:    After 2013 Blocks, About 14.1 days

To be specific about that

The block change is the average over 2016 blocks
(well actually it's 2015 due to a bug when it was first written but ignoring that ...)

A lot of these 'next diff' estimate sites base their estimate only on the blocks since the last change.
So yeah if you base the estimate for the next (2015) blocks on a few ... or even a few hundred ... it will almost certainly be way off.

Wait until there's about 1008 (half way) and it could be a closer estimate ... as long as there's no large amount of new hardware in the 2nd week ...

This change it was 18.1% but early on some of the sites were saying well over 20% some even 30% or more ...
79102380900.225983 -> 93448670796.32380676

Yay pool currently over 6.5PH

[PPOC]

And it goes on and on 

Bitcoin Difficulty:    93,448,670,796
Estimated Next Difficulty:    108,641,439,562 (+16.26%)
Adjust time:    After 2013 Blocks, About 14.1 days

To be specific about that

The block change is the average over 2016 blocks
(well actually it's 2015 due to a bug when it was first written but ignoring that ...)

A lot of these 'next diff' estimate sites base their estimate only on the blocks since the last change.
So yeah if you base the estimate for the next (2015) blocks on a few ... or even a few hundred ... it will almost certainly be way off.

Wait until there's about 1008 (half way) and it could be a closer estimate ... as long as there's no large amount of new hardware in the 2nd week ...

This change it was 18.1% but early on some of the sites were saying well over 20% some even 30% or more ...
79102380900.225983 -> 93448670796.32380676

Yay pool currently over 6.5PH

Sweet, 18% diff jump and 30% pool jump. Keep it up!

[not.you]

Yay pool currently over 6.5PH

Some of these big miners are fickle.

[usukan]

Yeah first block after increased difficulty 

Sounds like this Diff is going to be a lucky one for us! Nothing like tackling a new higher diff with the first block of that diff. I've always thought that the first block of a UTC day by a pool signals a good day for that pool. I know it's all BS but why not....

Kano was 2nd block at higher diff

but yes was thinking same spiritual thoughts of luck

[kano]

Yay pool currently over 6.5PH

http://vignette1.wikia.nocookie.net/adventuretimewithfinnandjake/images/f/f0/And_its_gone_original.jpg/revision/latest?cb=20130209022103

Some of these big miners are fickle.

Well I know some of what's going on, so hopefully it will be back.
But we'll see. Can only hope

[usukan]

@ZachM I love your pool monitor the emails notifying of a block find are great.

Thanks, glad you like it.

@ZACHM

Since everyone says this is great - I thought I would try.

Keep getting this error

API key invalid. Please double check your API key and try again!

retried and double checked (key correct as pasted) - does it take a while for a new API key to start working (be valid)?

also another question - For LOW Hashrate notification - do you enter a low total for all workers - or a low limit for any individual worker?  I assume its total for all workers.

Thanks

[kano]

...
retried and double checked (key correct as pasted) - does it take a while for a new API key to start working (be valid)?
...

Immediate on the pool.
The current valid key is the one it shows you on the Account->User Settings page
Though the actual key is just the Hex code.
...&api=00000000000000000000000000000000&json=y...
Just the blue part (whatever value yours is) that's also at the top.

[usukan]

...
retried and double checked (key correct as pasted) - does it take a while for a new API key to start working (be valid)?
...

Immediate on the pool.
The current valid key is the one it shows you on the Account->User Settings page
Though the actual key is just the Hex code.
...&api=00000000000000000000000000000000&json=y...
Just the blue part (whatever value yours is) that's also at the top.

Thanks Kano

Yes - I got the API key on Kano site no problems (generated new one - first one)

but when I enter it on ckpoolmonitor it says invalid try again?

username ok - check
APIkey OK - check (pasted direct from Kano site) - suppose you just past key - not the whole /index.php?k=api&username=usukan&api=6e91XXXXXXXXXXXXXXXXXce815&json=y
BTC address blank (cos I dont use BTC address) - check
Primary email OK - check

zilch - try again

[kano]

I don't know about his monitor's workings ... I don't use it ... I already have way too many monitors for the pool

My block monitors are pretty quiet, this morning's block didn't wake me up, I woke up about 15min later, but yesterday's block did.

But the pool alerts, if anything happens, (and alert me within about 60s) ... yeah they'll wake me up no matter what coz they are a lot louder and keep repeating more than every minute until I fix the problem or the problem fixes itself.

[ZACHM]

username ok - check
APIkey OK - check (pasted direct from Kano site) - suppose you just past key - not the whole /index.php?k=api&username=usukan&api=6e91XXXXXXXXXXXXXXXXXce815&json=y
BTC address blank (cos I dont use BTC address) - check
Primary email OK - check

zilch - try again

Your username is not correct.

I know it is telling you the APIKey is bad, but it needs both the username and APIKey, it happens to be the username that is wrong in this case.

also another question - For LOW Hashrate notification - do you enter a low total for all workers - or a low limit for any individual worker?  I assume its total for all workers.

Thanks

Yes, low hashrate for the total of all workers.

[kano]

username ok - check
APIkey OK - check (pasted direct from Kano site) - suppose you just past key - not the whole /index.php?k=api&username=usukan&api=6e91XXXXXXXXXXXXXXXXXce815&json=y
BTC address blank (cos I dont use BTC address) - check
Primary email OK - check

zilch - try again

Your username is not correct.

I know it is telling you the APIKey is bad, but it needs both the username and APIKey, it happens to be the username that is wrong in this case.
...

Oh, heh didn't think to check the database

Nope, his username is correct (unless he's added spaces somewhere we can't see)
The parts of the key he's shown are correct also.

[ZACHM]

username ok - check
APIkey OK - check (pasted direct from Kano site) - suppose you just past key - not the whole /index.php?k=api&username=usukan&api=6e91XXXXXXXXXXXXXXXXXce815&json=y
BTC address blank (cos I dont use BTC address) - check
Primary email OK - check

zilch - try again

Your username is not correct.

I know it is telling you the APIKey is bad, but it needs both the username and APIKey, it happens to be the username that is wrong in this case.
...

Oh, heh didn't think to check the database

Nope, his username is correct (unless he's added spaces somewhere we can't see)
The parts of the key he's shown are correct also.

On my site he has his username as usukanbay

[kano]

...
On my site he has his username as usukanbay

Well that wouldn't work now would it

[usukan]

username ok - check
APIkey OK - check (pasted direct from Kano site) - suppose you just past key - not the whole /index.php?k=api&username=usukan&api=6e91XXXXXXXXXXXXXXXXXce815&json=y
BTC address blank (cos I dont use BTC address) - check
Primary email OK - check

zilch - try again

Your username is not correct.

I know it is telling you the APIKey is bad, but it needs both the username and APIKey, it happens to be the username that is wrong in this case.
...

Oh, heh didn't think to check the database

Nope, his username is correct (unless he's added spaces somewhere we can't see)
The parts of the key he's shown are correct also.

On my site he has his username as usukanbay

Hey thanks and sorry for my mistake. Too many damn usernames to keep track. Will fix when home.

Cheers usukan

[ZACHM]

...
On my site he has his username as usukanbay

Well that wouldn't work now would it

Only if you had your api setup to say "well that's close enough".  

One of those easy mistakes, I've definitely done things like that.
Check it 10 times thinking yeah everything is fine, why the hell isn't it working.
Then the 11th time you look at it and notice that you typed fast and wrote CAt instead of Cat.

He probably uses both usernames and typed the wrong one without even thinking about it.

edit: yup just saw your post above.