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

[d57heinz]

Guys, doesn't it look for you like we have some issues with invalid shares?

That's how pool looks right now:

KanoPool:     22,098.71THs
Shares:     703,336,606,279 (51.55%)
Invalids:     25.4M (21.5%) · 104.5G (12.9%)
Last    Block
Pool:     40h 56m (495143)
Network:     2m 27s (495434)

Odds are it is old hardware. For example, Canaan has removed a majority of their hardware, but they probably leave old S7 or stuff running which would have a lot of invalids. Same goes for Cobra etcetera. That is my guess.

I just sent a message to nicehash thread. Would it have anything to do with the insanely high diff they have on our machines.  S9 65536 diff. Lowest Vardiff will drop. Same goes with s3 etc. I have about a 4% loss just in rejects due to high diff also my local work completed showing on s3 since they remove it on s9 is almost double that of accepted shares.  Could this be a problem. A form of inadvertent block withholding. Nicehash being slow to push shares is causing stales etc. just curious

BR

[1713522019]

1713522019

[1713522019]

1713522019

[kano]

Kano,

I'm sure you're already aware and you have your reasons, but have you thought about utilizing CloudFlare? They offer unlimited DDOS mitigation and their CDN might take a little load off the server. Anyway, it might make it so you don't have to remove login functionality while the DDOS is in effect.

Firstly, Cloudflare wont help,
... and I'd have to give them control of my SSL certificate which no one in their right mind would do
who has a site that deals with something of great value.

and of course when was the last time you noticed a DDoS on my web site ... they aren't rare, just rarely have an effect
In this case I just have a command I wrote to deal with it, that doesn't stop anyone using the site except logging in.

[kano]

Guys, doesn't it look for you like we have some issues with invalid shares?

That's how pool looks right now:

KanoPool:     22,098.71THs
Shares:     703,336,606,279 (51.55%)
Invalids:     25.4M (21.5%) · 104.5G (12.9%)
Last    Block
Pool:     40h 56m (495143)
Network:     2m 27s (495434)

Odds are it is old hardware. For example, Canaan has removed a majority of their hardware, but they probably leave old S7 or stuff running which would have a lot of invalids. Same goes for Cobra etcetera. That is my guess.

I just sent a message to nicehash thread. Would it have anything to do with the insanely high diff they have on our machines.  S9 65536 diff. Lowest Vardiff will drop. Same goes with s3 etc. I have about a 4% loss just in rejects due to high diff also my local work completed showing on s3 since they remove it on s9 is almost double that of accepted shares.  Could this be a problem. A form of inadvertent block withholding. Nicehash being slow to push shares is causing stales etc. just curious

BR

I try to block not-nicehash as much as possible since nothing good comes of having miners from there mining here.

Remember that long double block, about half of that hash rate came from there ... so one single source of shares had VERY bad luck ... ... ... not in any way definitive proof ... but I certainly consider it better to stop a single source of horrible bad luck, than to wait to find it's actually 10 blocks of lost blocks and absolutely no recourse if we find it is the cause (they specifically state they will keep the BTC) ... ... ...

I've also blocked an IP of not-nicehash once before that had really bad luck.

The simple problem is that EVERYONE mining on the pool must trust EVERY single physical miner mining through not-nicehash,
Yet mining through not-nicehash has a clear financial advantage for any of them to at least sometimes withhold blocks, in a simple way that they will also never be caught by not-nicehash.
... and those miners pointed at not-nicehash get paid PPS ... which means it doesn't matter if they find blocks or not, they'll still be paid.

We're dealing with a lot of money ... and a lot of people in this world are easily swayed to make decisions that are to their own financial advantage, that may not be to the advantage of others.
To think otherwise is simple foolishness.

[wuhanyan21]

I can only hope we stay at this size for as long as it can be. We will receive less but bigger inputs, making us save on transaction fees. And we still are finding 4 blocks per difficulty, which is good to fight variance, something a 1-2 block per difficulty pool would not be able to do.

[MEARK]

I just started using the ckpool android app about a week ago. Is it possible the app is being used as part of a DDos attack?
I like the ability to check my hash rate and to get an alert when the pool finds a block. It does check it every 10 minutes or so.
Just wondering. I realize the "distributed" part of the attack means it comes from a lot of different sources, but there is the possibility of over 900 users hitting your pool info at whatever interval the app is set for.

I've been using the CKPool android app for a while too.  Last week I got a whole bunch of block alerts coupled with "your hashrate has dipped below... " alerts... I got really excited that we scored a string of blocks until I realized how unlikely that really was given our luck lately  

Then it just happened again this morning.  Thought we had a block, but nope.  And got the same "your hashrate dipped" alert as well.

App problem, or related to the DDoS reported by Kano, or... ?  

Thanks all.  Still hanging in this pool since I started mining over the summer... I will be sacrificing a TURKEY tomorrow... two in fact... that must count for something!

*Edit:  crikeys, can you tell I really don't post too many messages here?? ha! 

[CooperAir]

Then it just happened again this morning.  Thought we had a block, but nope.  And got the same "your hashrate dipped" alert as well.

App problem, or related to the DDoS reported by Kano, or... ?  

Same here. Also got a flood of false notifications.

[kano]

Then it just happened again this morning.  Thought we had a block, but nope.  And got the same "your hashrate dipped" alert as well.

App problem, or related to the DDoS reported by Kano, or... ?  

Same here. Also got a flood of false notifications.

Might be the DDoS/restart?
THt was about 4:10am UTC to 4:35

[minergain.com]

and of course when was the last time you noticed a DDoS on my web site ... they aren't rare, just rarely have an effect
In this case I just have a command I wrote to deal with it, that doesn't stop anyone using the site except logging in.

Kano, do you have memcached running on your site?  how much ram is there?  My strandvision site has a home built ddos system using memcached (so it is fast) that auto slows all non important requests if the server load gets too high.  It also counts hits from each class c ip address range.  If it exceeds the max per minute hits, then the system instantly dies (for that ip address) for a day.  If they do not visit again for a minute, the memory is released.  I do have white lists for paying customers to prevent issues.  Anyway it sounds like you do not have issues with it, but if you do, this type of system does not take long to implement.  PM me if you would like details.

[minergain.com]

Might be the DDoS/restart?
THt was about 4:10am UTC to 4:35

CkMonitor does issue a notice every time your server restarts and is between their 5 minute check-in time.

[rifleman74]

A pumpkin pie was sacrificed in the name of the next block.

[Steamtyme]

Hey,

I just switched over to the pool last night. Figured it was as good a time as any, I did create a username but had issues logging in, and pointing a worker under that username.
Not sure if it had to do with the login issues last night, but I just used a BTC address, I'm wondering after my ramp up will I be able to switch over to using my username or would that cause me to go through a ramp up period again?

Thanks

[PeaMine]

ive got a s9 13.5 and a ebit e9+ 9.5 running on the same worker in and my invalids are only at .065 % is this the norm?

Do you have a screen shot?
For the S9, the only % is for Hardware Errors, which are different than Stales or Invalid Shares I believe.
Look at the Discarded, Rejected, and Stale columns.

58,453 Accepted
497 Rejected
438,883 Discarded
15 Stale

58453/439395 = 0.133 or around 13%, so around 1 out of 8 are invalid
S9 and S7 both have around these levels for me.

[overcon]

Hey,

I just switched over to the pool last night. Figured it was as good a time as any, I did create a username but had issues logging in, and pointing a worker under that username.
Not sure if it had to do with the login issues last night, but I just used a BTC address, I'm wondering after my ramp up will I be able to switch over to using my username or would that cause me to go through a ramp up period again?

Thanks

If you just joined last night then changing anything isn't going to impact your 5ND much at this point.

[rifleman74]

Hey,

I just switched over to the pool last night. Figured it was as good a time as any, I did create a username but had issues logging in, and pointing a worker under that username.
Not sure if it had to do with the login issues last night, but I just used a BTC address, I'm wondering after my ramp up will I be able to switch over to using my username or would that cause me to go through a ramp up period again?

Thanks

change it now, you changing to a different username will start from scratch.

[Toll-Booth-Jim]

ive got a s9 13.5 and a ebit e9+ 9.5 running on the same worker in and my invalids are only at .065 % is this the norm?

Do you have a screen shot?
For the S9, the only % is for Hardware Errors, which are different than Stales or Invalid Shares I believe.
Look at the Discarded, Rejected, and Stale columns.

58,453 Accepted
497 Rejected
438,883 Discarded
15 Stale

58453/439395 = 0.133 or around 13%, so around 1 out of 8 are invalid
S9 and S7 both have around these levels for me.

Not a screen shot but here are the current figures from the s9, the e9+ doesn't have all that the s9 does.

diff: 10.8k
getworks: 10,487
accepted: 89,352
diffA: 986,371,488
diffr: 677,075
rejected: 61
discarded: 167,725 which is the what were talking about I guess, I didn't see it before.
stale: 26
local work: 15,736,184
best share: 1750787685
time frame: 3d15h16m48s

[Toll-Booth-Jim]

lol I think one of my boards in my s9 is having some issues it's hw is 6021 the other 2 are 42 and 46.

[minergain.com]

lol I think one of my boards in my s9 is having some issues it's hw is 6021 the other 2 are 42 and 46.

If yours is, then so is mine which has been that way for weeks with full hashing...  Mine is 8188, 80 and 91

[Toll-Booth-Jim]

lol I think one of my boards in my s9 is having some issues it's hw is 6021 the other 2 are 42 and 46.

If yours is, then so is mine which has been that way for weeks with full hashing...  Mine is 8188, 80 and 91

anyone else have input on this?  lol I have no idea if this is ok or if it's actually a problem with the board.

[bussumseheide]

lol I think one of my boards in my s9 is having some issues it's hw is 6021 the other 2 are 42 and 46.

If yours is, then so is mine which has been that way for weeks with full hashing...  Mine is 8188, 80 and 91

better look at the relative error instead of absolute numbers. At the row HW look at the % value, normal/acceptable value is about 0.001% , value higher than 0.01% might be concerning

[stormwind]

ive got a s9 13.5 and a ebit e9+ 9.5 running on the same worker in and my invalids are only at .065 % is this the norm?

Do you have a screen shot?
For the S9, the only % is for Hardware Errors, which are different than Stales or Invalid Shares I believe.
Look at the Discarded, Rejected, and Stale columns.

58,453 Accepted
497 Rejected
438,883 Discarded
15 Stale

58453/439395 = 0.133 or around 13%, so around 1 out of 8 are invalid
S9 and S7 both have around these levels for me.

Not a screen shot but here are the current figures from the s9, the e9+ doesn't have all that the s9 does.

diff: 10.8k
getworks: 10,487
accepted: 89,352
diffA: 986,371,488
diffr: 677,075
rejected: 61
discarded: 167,725 which is the what were talking about I guess, I didn't see it before.
stale: 26
local work: 15,736,184
best share: 1750787685
time frame: 3d15h16m48s

Look here https://kano.is/index.php?k=workers