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

[xgeniy]

1-2 request per minute is normal from 1 ip
if <5 times per minute then the ban on the hour. so correct

p.s. miners statistics collection is part of the job. and it is necessary to ensure continuous monitoring of the farm. if there is a restriction I do not know when to stop working miners

[sorry2xs]

i had easy reload set for almost a month to 300 seconds and i woke up this morning banned

[PsyDafKe]

Hmmm, woke up with a nice green greeting on the blocks page...
also got banned... but was clicking back and forward between "blocks" and "rewards" to compare.
waited 15-20 minutes (not touching/trying), and can get back in.

Think Kano is still tuning the restriction, so just don't do crazy refreshes :p

BTW: congrats at the blockfinders on this beautiful (rainy) saturday!

[sorry2xs]

banned or not the blocks was a nice refreshing wake up

[VRobb]

Agreed, love waking up to a Saturday Triple Block Party and seeing multiple blocks maturing to tasty payouts! Yum! 

Edit-actually a 5 block Saturday already for the pool, let's keep 'em popping!

[AriesIV10]

Restarted my computer and All is OK now.

[kano]

Well I'm sorta disabling it for now, but without undoing the code change.
It's all new code and seems it will require a little more work and adjustment.

I've cleared out most of the bans but a few still keep sneaking in.
They'll have to wait until tomorrow, it's 2am here and I'm about to pass out

One thing that will clear it for the few that are left (8 bans out of the original 150 it generated )
If you try to access the same page that gave you a ban it should new clear it

Anyway I'll sort it all out tomorrow

[citronick]

I am banned to kingdom come ...  seems my auto-refresh on the critical kano stat pages - are causing me to be banned....

I monitor key kano stats using 4 x critical information. It gives me a quick glance :

1. if my workers and rentals are performing to my liking, via the workers page - this will give me some indication of which miner or rental is in question (using this in addition to Zach's monitor).
2. "user shift graph" - where i can monitor the 5ND and how far off my total hash is at. This will give me perspective on what size of rental should I get ready for and also gives me a chance to book rentals at a certain date and time.
3. "user rewards page" - where i get a quick glance on latest payout ratios so that i can decide on how much rental should i allocate to be within prefered average - this is probably the most important for me because i keep x% of BTCs payout for rental fund on a daily basis - because I cant expand my miner farm anymore due to high cost of electricity.
4. of course - the blocks main page - where i track when the next "block day" ... and record their occurrence in a separate spreadsheet - this is my own private sorcery project where I hope to predict when block parties likely to occur, when is the next block etc. using some non-sensical formula - for fun and my own amusement....

In Chrome, I use auto-refresh widget, set at 15/30/45/60 seconds.

If the above "auto-refresh" is not allowed:

1. please advise what is the "number" seconds that is acceptable to keep kano server in tip top condition.
2. If #1 is not allowed, is there a "quick public page" that shows some key anonymous data - even some indication on which worker is down etc.
3. can kano.system collects key information and send half-daily / daily "reports or summary" to members via email / text?
4. if I may propose, that setup "premium" members, ie. if I donate/pay x BTC per month, gets unlimited access to kano stats - its just a proposal, because i need the stats to be able to manage kano.is as profitable as possible.

I apologize if this is a lengthy rant, the above points are only important to me and may not be the same as other members.

Peace.

[thedreamer]

That auto refresh is way too fast.

No need to watch the pool that closely as stats are on a delay anyways. Also rentals are always 15 minutes behind what's shown also on their end (at least at MRR) so again, that refresh rate is useless.

Set it to a 5 minute refresh and be done.

Works perfectly for me, as even a refresh every second will not do anything extra for me or you in regards to the pool or the hash rate.

It's not like daytrading stocks, where every minute matters. Here it does not.

[philipma1957]

That auto refresh is way too fast.

No need to watch the pool that closely as stats are on a delay anyways. Also rentals are always 15 minutes behind what's shown also on their end (at least at MRR) so again, that refresh rate is useless.

Set it to a 5 minute refresh and be done.

Works perfectly for me, as even a refresh every second will not do anything extra for me or you in regards to the pool or the hash rate.

It's not like daytrading stocks, where every minute matters. Here it does not.

yeah  you are correct.

we make 1 to 8 blocks a day.

so 1 every 10 minutes would be 6 per hour and 144 a day.

since 8 into 144 = 18  even a 10 minute refresh time is 18 looks for each block  on a day where we make 8 blocks.

A good way of looking at refresh rate is how often do we do 2 blocks under 10 minutes?   since if you look every 10 minutes the most that happens is there is one block.

I believe of all 550 plus blocks  three times we did 2 in 10 minutes or less.

So even a ten minute refresh works.

[thedreamer]

I actually only check the site every few hours as it's mentally draining to watch live stats IMO.

5minutes is the lowest I'd even consider an auto refresh if I needed to actually watch it.

[citronick]

That auto refresh is way too fast.

No need to watch the pool that closely as stats are on a delay anyways. Also rentals are always 15 minutes behind what's shown also on their end (at least at MRR) so again, that refresh rate is useless.

Set it to a 5 minute refresh and be done.

Works perfectly for me, as even a refresh every second will not do anything extra for me or you in regards to the pool or the hash rate.

It's not like daytrading stocks, where every minute matters. Here it does not.

yeah  you are correct.

we make 1 to 8 blocks a day.

so 1 every 10 minutes would be 6 per hour and 144 a day.

since 8 into 144 = 18  even a 10 minute refresh time is 18 looks for each block  on a day where we make 8 blocks.

A good way of looking at refresh rate is how often do we do 2 blocks under 10 minutes?   since if you look every 10 minutes the most that happens is there is one block.

I believe of all 550 plus blocks  three times we did 2 in 10 minutes or less.

So even a ten minute refresh works.

Thanks guys for the perspective and recommendations - I have set it to 5/6/7/10 minutes. Hope it would not trigger anymore  bans.

[thedreamer]

:facepalm: @ the person renting huge rental on NH/WH and raising up the prices again. SMH.

[philipma1957]

That auto refresh is way too fast.

No need to watch the pool that closely as stats are on a delay anyways. Also rentals are always 15 minutes behind what's shown also on their end (at least at MRR) so again, that refresh rate is useless.

Set it to a 5 minute refresh and be done.

Works perfectly for me, as even a refresh every second will not do anything extra for me or you in regards to the pool or the hash rate.

It's not like daytrading stocks, where every minute matters. Here it does not.

yeah  you are correct.

we make 1 to 8 blocks a day.

so 1 every 10 minutes would be 6 per hour and 144 a day.

since 8 into 144 = 18  even a 10 minute refresh time is 18 looks for each block  on a day where we make 8 blocks.

A good way of looking at refresh rate is how often do we do 2 blocks under 10 minutes?   since if you look every 10 minutes the most that happens is there is one block.

I believe of all 550 plus blocks  three times we did 2 in 10 minutes or less.

So even a ten minute refresh works.

Thanks guys for the perspective and recommendations - I have set it to 5/6/7/10 minutes. Hope it would trigger anymore  bans.

I would like to know if 5/6/7/10 fixes the problem lets us know.

[d57heinz]

That auto refresh is way too fast.

No need to watch the pool that closely as stats are on a delay anyways. Also rentals are always 15 minutes behind what's shown also on their end (at least at MRR) so again, that refresh rate is useless.

Set it to a 5 minute refresh and be done.

Works perfectly for me, as even a refresh every second will not do anything extra for me or you in regards to the pool or the hash rate.

It's not like daytrading stocks, where every minute matters. Here it does not.

yeah  you are correct.

we make 1 to 8 blocks a day.

so 1 every 10 minutes would be 6 per hour and 144 a day.

since 8 into 144 = 18  even a 10 minute refresh time is 18 looks for each block  on a day where we make 8 blocks.

A good way of looking at refresh rate is how often do we do 2 blocks under 10 minutes?   since if you look every 10 minutes the most that happens is there is one block.

I believe of all 550 plus blocks  three times we did 2 in 10 minutes or less.

So even a ten minute refresh works.

Thanks guys for the perspective and recommendations - I have set it to 5/6/7/10 minutes. Hope it would trigger anymore  bans.

I would like to know if 5/6/7/10 fixes the problem lets us know.

i had it set to just under 24 mins or was it 26  .. whatever the default logout value is for php.. just keep it under that and you wont have to keep loggin in..

"It depends on the server configuration or the relevant directives (session.gc_maxlifetime) in php.ini. Typically the default is 24 minutes (1440 seconds), but your webhost may have altered the default to something else." 
http://stackoverflow.com/questions/9904105/php-sessions-default-timeout

Best Regards
d57heinz

[bctmke]

Great block run overnight!  I'm all for Kano's changes re: the website.  Let's see how they shake out!

[kano]

...
I would like to know if 5/6/7/10 fixes the problem lets us know.

It was effectively all disabled from when I last posted but yeah there where a few IPs that didn't seem to clear properly.
Anyone else would be a bug at the moment in the event processing, but anyway that run last night (it's now morning here) gave me some real data to use to sort out what it needs to be.

I'll make the limit higher than this, and may need to make more brackets for counting limits, but seriously, if you are hitting the web site more than a few times a minute, you are wasting your and the web site's time.

There's 2 numbers that are relevant:

1) The 'ckpool' hash rates are only updated once per minute.
Most miner hash rates (specifically all Bitmain miners) are far from reliable even after an hour of mining, so the ckpool<->ckdb code is, by design, one hash rate update per minute, per worker.
At the moment, as the web site says, there's over 8100 workers on the pool and that means roughly 8100 updates transferred per minute between them, or about 135 updates per second. That's more than enough It's not a limiting issue, it's simply that the numbers are more than accurate enough as they are, and doing it even more often won't make them more accurate.
This of course also means that if you use hash rate to detect a problem with your miner, you won't get a better detection by polling any more than a few times a minute (and it's not possible to get a better result since the hash rate isn't a dynamic value no matter how we configured the pool)

2) if you poll the web/API to detect a miner failure on "Last Share", the actual probability of getting a 15s share is:
Expected average share 18SPM (18 shares per minute) so 3.3333 seconds average per share.
A 15s share would be the same as a 450% "Diff"
CDF for 450% (and 900%) is:

Code:

0.98889100346176  450.000%  1 in 90.0
0.99987659019591  900.000%  1 in 8103.1

So, on average, one in 90 shares is actually expected to average 15s or more, or roughly 288 shares per day.
With 900% (30s) one in ~8100 shares is expected to average 30s or more, or roughly, 3 shares per day.
So any "miner failure" detection based on "Last Share" would average 3 false positives a day is you set the limit to 30s.
I'd suggest 45s minimum for that sort of detection.

Edit: actually to show the 45s and 60s numbers:

Code:

0.99999862904091  1350.000%  1 in 729416.4
0.99999998477002  1800.000%  1 in 65659969.2

So on average, no share for 45s would average about once a month.
If you have 10 miners, then you'd average about 10 false positives a month.

Using 60s, on the other hand, you'd expect to average one false positive per miner per ... 7.4 years
So maybe I should say, anyone doing "Last Share" detection, should use 60s and rarely if ever get a false positive.

[wolfen]

Thanks kano for all your hard work.
We are all trying to get that next block for the team.

[kano]

Heh well the next block - 399390 - was an interesting one
Confirmed the last 2 payouts: 399279 and 399289

But what actually happened was (of course) that 399289 came due at block 399389, I did the payout, got it into the pool work, then less than 60s later we got a block to confirm them both!
Nice timing.

It also means that the payout caused the block, but of course you can't predict that in advance

[wolfen]

It's magic I tell ya!