Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1480. (Read 5352420 times)

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Web site is temporarily unavailable for logins.
I stopped it for a minute but I've restarted it again.
There's a web botnet (a lot bigger than the last one) attacking at the moment.
API is OK now also.
Edit: mining is unaffected.
newbie
Activity: 22
Merit: 0
Next in line!  Hmm maybe it doesn't work exactly like that...
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Abramov ... who won the April Avalon6 ... you need to read your email ...
Abramov ... who won the April Avalon6 ... you need to read your email ...

If you don't reply in a few days, I'll give the Avalon6 to the next in line.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Just a warning for people, someone at IP address 86.102.20.79 sent a tiny botnet at the pool web site, guessing passwords.
They, surprisingly, guessed the password for one account, though no one else has been affected.
I guess the password was too simple? (I don't know since I don't know what anyone's password is, it's not logged or stored anywhere)
I can't find any other accounts that were affected, so it appears to just be the one account.

The pool always sends you an email if anything changes, including your password or email or payout address, so you will always know if someone else logs into your account and changes anything like that.
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
Like if you have an old s3 thats over clocked with some burnt out chips you give a power source that won't shut off like it should or like this rental I just cancel because it had half rejects...  You can always just find a trusted miner and rent old school.  Miners usually love getting advance coin.  A few days or a week up front is a bill they can pay early or a rig they can buy early.  The should be a thread for that... Don't expect compensation like MRR, just pick a stable miner.  Prices are way to high on all renting on sites right now, we are going to have to stop paying unreasonable prices or it will never change.  NH eats orders up and drops them at will.  They all have choppy connections, and %95-150 of diff estimate rental prices.  I'm not sure of the point.  People renting to boost Kano has just killed any profitability in the renting market.  

Yeah I backed off renting.  Will just do core mining real gear with32th
sr. member
Activity: 261
Merit: 250
The pool has been having some bad luck, but nothing to worry about.  True, it is some of the worst luck in the history of the pool (judging by the 25 block luck avg at https://kano.is/index.php?k=luck), but it happens.  The one good thing is the last time the pool luck was this bad it lasted for about 50 blocks and took place from about 09/15 through 11/15.  Those 50 blocks of bad luck took 2 months to get through, while the last 50 blocks of bad luck this time has only taken 2 weeks (due to the much higher speed of the pool now).  So, this should pass quickly.

One thing that isn't just simply bad luck is the possibility that other pools are trying to orphan blocks at this pool.  While F2 has 25% of the hashrate, that isn't enough for them to put effort into orphaning blocks at this pool.  It would hurt them more than it would hurt this pool, and it doesn't look like they are doing it.  While 410419 might look like a case of this, it was unusual as it took F2 finding 2 blocks in a row to pull this off.  What really happened is they found a block within a couple of seconds of Kano and then got lucky finding a second block.  It can sometimes happen, but shouldn't worry anyone.  Like I said, if F2 were to try to orphan blocks at this pool, it would hurt them more than it would hurt this pool.  In addition, there would be a pattern of this happening and I don't see a pattern in the list of orphans from this year:

410419 - F2
410208 - BTCC
406906 - BW
406197 - Antpool
402609 - Unknown
397182 - Bitfury

F2 just did it one time, it was bound to happen sooner or later.  There was no conspiracy when BTCC, BW, Antpool, etc did it, so no need to think of a conspiracy when F2 does it.


legendary
Activity: 952
Merit: 1003
Now we're cookin' again...  Roll Eyes
sr. member
Activity: 277
Merit: 250
That's what rebooting the system does .... BLOCKS!

I vote for a weekly pool reboot!!!!
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
There is always sunshine after rain at kano.is!

2 early blocks is great start to the day -- our last rebound a few weeks ago gave us 11 blocks!

Common blocks !!!
sr. member
Activity: 546
Merit: 253
Great seeing two blocks in such a short time.
full member
Activity: 238
Merit: 100
Like if you have an old s3 thats over clocked with some burnt out chips you give a power source that won't shut off like it should or like this rental I just cancel because it had half rejects...  You can always just find a trusted miner and rent old school.  Miners usually love getting advance coin.  A few days or a week up front is a bill they can pay early or a rig they can buy early.  The should be a thread for that... Don't expect compensation like MRR, just pick a stable miner.  Prices are way to high on all renting on sites right now, we are going to have to stop paying unreasonable prices or it will never change.  NH eats orders up and drops them at will.  They all have choppy connections, and %95-150 of diff estimate rental prices.  I'm not sure of the point.  People renting to boost Kano has just killed any profitability in the renting market.  
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Another Block, this one by AlpMine with his 5th kano block!  Cheesy
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I know of a few ways they can do it.   

so to everyone here that is renting  from NH / WH   consider that

   f2pool can send dead hashers to   WH/NH  with ease   


Can you explain what you mean by "send[ing] dead hashers?"
When you pay for miners at *Hash - you have no idea what the miners are and what they are doing.
*Hash don't care either coz they get paid BEFORE you mine and they wont lose anything.
The people who own the miners will get paid no matter what also.
Thus someone could provide "bad hash power" on *Hash and no one would know unless they mined a VERY large amount and kept track of the statistics ... ... ...


But my question is more along the lines of what exactly is "bad hash power" or "dead hashing?" I realize that service drops, latency, *Hash's algo switching interruptions, etc could result in stale shares, but apart from that I'm not clear on how a person could dispatch miners that are "dead/bad." 
Software dropping shares/blocks, or even using faulty hardware that has no use.
e.g. someone may have hardware that can't find blocks that they would normally not use it at all, or have given up on coz they can't fix it for a reasonable cost, but ... point it at *Hash ...
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
Block by GLORYTrading!  That is his 21st kano block!
much better   maybe we have a derby day right here with kano.is
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block by GLORYTrading!  That is his 21st kano block!
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
I know of a few ways they can do it.   

so to everyone here that is renting  from NH / WH   consider that

   f2pool can send dead hashers to   WH/NH  with ease   


Can you explain what you mean by "send[ing] dead hashers?"
When you pay for miners at *Hash - you have no idea what the miners are and what they are doing.
*Hash don't care either coz they get paid BEFORE you mine and they wont lose anything.
The people who own the miners will get paid no matter what also.
Thus someone could provide "bad hash power" on *Hash and no one would know unless they mined a VERY large amount and kept track of the statistics ... ... ...


But my question is more along the lines of what exactly is "bad hash power" or "dead hashing?" I realize that service drops, latency, *Hash's algo switching interruptions, etc could result in stale shares, but apart from that I'm not clear on how a person could dispatch miners that are "dead/bad." 

sure set your gear to discard every hash over 177  diff is 178  you get paid and never hit a block.

or be more clever set you gear to discard every hash over 185 so you still hit a block here and there but you  discard a ton of blocks.

take a quality  programer to do it.

and you need a website like nicehash to help you hide your actions.

you need solid resources to pull it off..

but if i point 5ph to westhash. set my rental price a tad low. say .0026 
and some grabs it and points it to kano.is a big hurt happens to kano.is
member
Activity: 117
Merit: 16
I know of a few ways they can do it.   

so to everyone here that is renting  from NH / WH   consider that

   f2pool can send dead hashers to   WH/NH  with ease   


Can you explain what you mean by "send[ing] dead hashers?"
When you pay for miners at *Hash - you have no idea what the miners are and what they are doing.
*Hash don't care either coz they get paid BEFORE you mine and they wont lose anything.
The people who own the miners will get paid no matter what also.
Thus someone could provide "bad hash power" on *Hash and no one would know unless they mined a VERY large amount and kept track of the statistics ... ... ...


But my question is more along the lines of what exactly is "bad hash power" or "dead hashing?" I realize that service drops, latency, *Hash's algo switching interruptions, etc could result in stale shares, but apart from that I'm not clear on how a person could dispatch miners that are "dead/bad." 
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I just bought a 25lb case of chicken fritters..... hopefully that'll inject some good juju into the pool .....

OR ....

Kano could reboot the whole system. That has ALWAYS worked in the past ....

:-)
Yeah there's a change to ckpool -ck did the other day and I want to add that in to help with the luck stats I do.
I've not made any changes to ckdb for that yet, but I'll be restarting the main pool in 2 hours at 00:10 UTC

This is the standard ckpool restart where most miners just see it as an immediate reconnect.
A small % of miners will failover (usually only around 1%) and will fail back within 5 minutes.
If your miner has difficulty handling reconnects then it may failover and not fail back (some buggy bitmain firmwares do that)
Done, without a hitch, at 00:13 UTC
About 2PH of miners never came back after 5 minutes - at a guess would be rentals.
legendary
Activity: 952
Merit: 1003
Repeat after me: There is nothing wrong with the pool. There is no way to game the system. The big pools can't do anything to small pools. There is no spoon conspiracy.

The only thing that's happened is a run of bad luck and fighting orphans with an overwhelmingly large pool.

Back to mining.

Mahalo (thanks).  Cool
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I just bought a 25lb case of chicken fritters..... hopefully that'll inject some good juju into the pool .....

OR ....

Kano could reboot the whole system. That has ALWAYS worked in the past ....

:-)
Yeah there's a change to ckpool -ck did the other day and I want to add that in to help with the luck stats I do.
I've not made any changes to ckdb for that yet, but I'll be restarting the main pool in 2 hours at 00:10 UTC

This is the standard ckpool restart where most miners just see it as an immediate reconnect.
A small % of miners will failover (usually only around 1%) and will fail back within 5 minutes.
If your miner has difficulty handling reconnects then it may failover and not fail back (some buggy bitmain firmwares do that)
Jump to: