Wow two blocks back to back awesome pt0x
Thanks pt0x
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1598. (Read 5352367 times)
March 20, 2016, 02:58:57 AM
Thanks pt0x
March 20, 2016, 02:42:29 AM
I'm sure it's been said before, but Kano and ck, thanks for everything. You're class acts, and the way you look out for the little guys and the community (& technology) as a whole is admirable.
Also a thanks to my fellow poolmates. I don't think I've met a group of kinder more helpful people on the entire Internet. Here's to many more blocks and a lot of fun!
Also a thanks to my fellow poolmates. I don't think I've met a group of kinder more helpful people on the entire Internet. Here's to many more blocks and a lot of fun!
March 20, 2016, 02:29:51 AM
Wow two blocks back to back awesome pt0x
March 19, 2016, 11:46:19 PM
I seem to recall someone a few years ago saying their chips didn't hash the full range or something. The numbers were something like 768 out of 1024 or equiv. Wonder if that has something to do with it.
I'm thinking it was BFL or the 55nm Bitfury. I'll look around and see if I can find the thread.
No, that's not a problem. It was bitfury chips but led to no problems like this whatsoever. I'm thinking it was BFL or the 55nm Bitfury. I'll look around and see if I can find the thread.
March 19, 2016, 11:34:42 PM
My partners and I are almost 12% of the total pool hashing power at the moment, so there better not be any block holding B.S . LET's GET EM BLOCKS!!!!!!!!!!!!!!
P.S What is weird is when I refresh my screen, it would show 78K diff, 103K, and 241, back to back. All within seconds. All over the map
Worker Name: Work Diff :Last Share Shares :Diff :Share Rate «Elapsed :Invalid Block % :Hash Rate
nhando1977.xx 103.933k 1s 49,930 8,095,268,587 4,627.49THs 3m 47s 0.127% 11.908% 3,940.25TH
Worker Name: Work Diff :Last Share Shares :Diff :Share Rate «Elapsed :Invalid Block % :Hash Rate
nhando1977.xx 241.912k 1s 50,026 8,110,065,783 4,641.64THs 4m 0s 0.127% 11.911% 3,940.25THs
Worker Name: Work Diff :Last Share Shares :Diff :Share Rate «Elapsed :Invalid Block % :Hash Rate
nhando1977.xx 134.959k 0s 50,735 8,232,320,761 4,643.27THs 5m 53s 0.125% 11.937% 3,966.67THs
Worker Name: Work Diff :Last Share Shares :Diff :Share Rate «Elapsed :Invalid Block % :Hash Rate
nhando1977.xx 74.918k 0s 52,379 8,520,257,838 4,623.40THs 10m 22s 0.121% 11.992% 4,012.51THs
P.S What is weird is when I refresh my screen, it would show 78K diff, 103K, and 241, back to back. All within seconds. All over the map
Worker Name: Work Diff :Last Share Shares :Diff :Share Rate «Elapsed :Invalid Block % :Hash Rate
nhando1977.xx 103.933k 1s 49,930 8,095,268,587 4,627.49THs 3m 47s 0.127% 11.908% 3,940.25TH
Worker Name: Work Diff :Last Share Shares :Diff :Share Rate «Elapsed :Invalid Block % :Hash Rate
nhando1977.xx 241.912k 1s 50,026 8,110,065,783 4,641.64THs 4m 0s 0.127% 11.911% 3,940.25THs
Worker Name: Work Diff :Last Share Shares :Diff :Share Rate «Elapsed :Invalid Block % :Hash Rate
nhando1977.xx 134.959k 0s 50,735 8,232,320,761 4,643.27THs 5m 53s 0.125% 11.937% 3,966.67THs
Worker Name: Work Diff :Last Share Shares :Diff :Share Rate «Elapsed :Invalid Block % :Hash Rate
nhando1977.xx 74.918k 0s 52,379 8,520,257,838 4,623.40THs 10m 22s 0.121% 11.992% 4,012.51THs
March 19, 2016, 11:15:50 PM
Dammit, seems like Shirlock Holmes won't be able to track this one. So what checks do we have in place today to safeguard us from this issue? So these bastard took a bunch of BTC somewhere around 46BTC after the deduction from us? Don't make me get Putin to chase down their ass! Not cool.
There's a critical number of shares beyond which it becomes highly improbable that miners haven't submitted a certain number of high shares. This is what all the database work kano has been doing over the last few weeks has been towards detecting so in future it should be picked up much sooner. This almost certainly went on for much longer on other pools in the past, and may well still be ongoing now, but don't be quick to blame any runs of bad luck on this issue as it takes a lot of shares to detect, but fortunately the larger the miner, the faster they'll be picked up (and Kano checks for patterns from groups of miners in similar places to see they're not splitting their hashes across multiple accounts to hide it.) 
March 19, 2016, 11:15:08 PM
Do you think it is possible for them to be redirecting the block finding shares at a local wallet and the rest of the garbage shares at the pools?
That's not possible.I did not think so. Was just trying to come up with a reason other than douchbagery ;/
March 19, 2016, 11:12:00 PM
Do you think it is possible for them to be redirecting the block finding shares at a local wallet and the rest of the garbage shares at the pools?
That's not possible. March 19, 2016, 11:11:33 PM
Dammit, seems like Shirlock Holmes won't be able to track this one. So what checks do we have in place today to safeguard us from this issue? So these bastard took a bunch of BTC somewhere around 46BTC after the deduction from us? Don't make me get Putin to chase down their ass! Not cool.
Well the checks in place are there for block withholding from quite a long time back.The "Acclaim" page shows me a lot more information than it shows anyone else
Every miner and some summarised stats (which you can see that it does that in the source php code)
I did once ban someone large from the pool for low luck that didn't actually signify proof of a problem
(proof being above 250BTC is an expensive proof)
They're a competitor and were having significant low luck here and at their pool - not bad enough to constitute withholding but I preferred the lesser problem of closing their account rather than possibly finding the problem continuing.
Anyway, I can now generate rather detailed stats on accounts using even block ranges, and look at those stats like I pasted on the previous page.
... and track miner connections ...
I check those when I process the payouts.
March 19, 2016, 11:09:14 PM
Do you think it is possible for them to be redirecting the block finding shares at a local wallet and the rest of the garbage shares at the pools?
March 19, 2016, 10:56:39 PM
Maybe it's the same group of equipment that was attacking Slush in 2014 then BTCGuild in early 2015. They know the rigs have shortcuts taken in their firmware and have been getting creative in hiding it because that's easier than admitting they've got a room full of shitty equipment. 
March 19, 2016, 10:49:34 PM
Dammit, seems like Shirlock Holmes won't be able to track this one. So what checks do we have in place today to safeguard us from this issue? So these bastard took a bunch of BTC somewhere around 46BTC after the deduction from us? Don't make me get Putin to chase down their ass! Not cool.
March 19, 2016, 10:45:37 PM
I guess I still cannot wrap my head around the motive for anyone doing this. Are they hoping that they can drive the pool luck down so that members leave and go.....where? Even if they could cause the pool luck to go down, how can they direct anyone to go where it would benefit them?
I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
Hanlon's razor - "Never attribute to malice that which can be adequately explained by stupidity, but don't rule out malice."I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
I doubt it started out as malice. Likely it started out as stupidity and has turned to malice over time.
Since they never respond when directly questioned/emailed, the most likely explanation is this was a batch of custom miners that were faulty right from the beginning, be it due to firmware or dodgy software, that had a 32 bit signed integer limitation somewhere in their design that cannot be now fixed, or is not worth the effort to fix, and have been mining under the radar for ages on other pools without being noticed. Now that they have been noticed, they have been moving from pool to pool to try and be not noticed and appear to have no intention to try and fix the issue.
What kind of hardware were they running?
look here: https://bitcointalksearch.org/topic/m.14226522
March 19, 2016, 10:42:42 PM
I guess I still cannot wrap my head around the motive for anyone doing this. Are they hoping that they can drive the pool luck down so that members leave and go.....where? Even if they could cause the pool luck to go down, how can they direct anyone to go where it would benefit them?
I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
Hanlon's razor - "Never attribute to malice that which can be adequately explained by stupidity, but don't rule out malice."I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
I doubt it started out as malice. Likely it started out as stupidity and has turned to malice over time.
Since they never respond when directly questioned/emailed, the most likely explanation is this was a batch of custom miners that were faulty right from the beginning, be it due to firmware or dodgy software, that had a 32 bit signed integer limitation somewhere in their design that cannot be now fixed, or is not worth the effort to fix, and have been mining under the radar for ages on other pools without being noticed. Now that they have been noticed, they have been moving from pool to pool to try and be not noticed and appear to have no intention to try and fix the issue.
What kind of hardware were they running?
March 19, 2016, 10:38:46 PM
I guess I still cannot wrap my head around the motive for anyone doing this. Are they hoping that they can drive the pool luck down so that members leave and go.....where? Even if they could cause the pool luck to go down, how can they direct anyone to go where it would benefit them?
I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
Hanlon's razor - "Never attribute to malice that which can be adequately explained by stupidity, but don't rule out malice."I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
I doubt it started out as malice. Likely it started out as stupidity and has turned to malice over time.
Since they never respond when directly questioned/emailed, the most likely explanation is this was a batch of custom miners that were faulty right from the beginning, be it due to firmware or dodgy software, that had a 32 bit signed integer limitation somewhere in their design that cannot be now fixed, or is not worth the effort to fix, and have been mining under the radar for ages on other pools without being noticed. Now that they have been noticed, they have been moving from pool to pool to try and be not noticed and appear to have no intention to try and fix the issue.
Now that I can understand...thanks ck!
March 19, 2016, 10:10:28 PM
I guess I still cannot wrap my head around the motive for anyone doing this. Are they hoping that they can drive the pool luck down so that members leave and go.....where? Even if they could cause the pool luck to go down, how can they direct anyone to go where it would benefit them?
I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
Hanlon's razor - "Never attribute to malice that which can be adequately explained by stupidity, but don't rule out malice."I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
I doubt it started out as malice. Likely it started out as stupidity and has turned to malice over time.
Since they never respond when directly questioned/emailed, the most likely explanation is this was a batch of custom miners that were faulty right from the beginning, be it due to firmware or dodgy software, that had a 32 bit signed integer limitation somewhere in their design that cannot be now fixed, or is not worth the effort to fix, and have been mining under the radar for ages on other pools without being noticed. Now that they have been noticed, they have been moving from pool to pool to try and be not noticed and appear to have no intention to try and fix the issue.
March 19, 2016, 09:56:09 PM
I guess I still cannot wrap my head around the motive for anyone doing this. Are they hoping that they can drive the pool luck down so that members leave and go.....where? Even if they could cause the pool luck to go down, how can they direct anyone to go where it would benefit them?
I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
I can see that it happened and that they did it intentionally but I just don't see the end game for the perpetrators. Maybe I just can't think like the bad guys!
March 19, 2016, 09:46:08 PM
Conspiracy theories. I still don't buy it. No one benefits from withholding blocks.
Other pools would if, e.g. I had not detected it and it had spread or even just continued.... by that I mean ... people might leave here and go somewhere else if the luck falls consistently.
Losing ~1% of the pool's blocks in not insignificant in my opinion ...
Of course if any pool has long term bad luck it's quite understandable and quite intelligent to leave them
We happen to have 110% luck during this ... so was really more like 111%
But you do need to consider the statistics and probabilities, not go hopping each time a pool gets a few blocks over 100% diff ......... as is expected to happen ... and hopping will not change your expected payout.
... e.g. slush's December luck was ~1 in 7633.6 chance of getting that luck in a month ... ~1 in 636 years
https://bitcointalksearch.org/topic/m.13482822
The worst luck we've had here was Red October.
But that was only 13 blocks (12 + the last one in September) with an average of ~168% diff
CDF[Erl] is 0.983642 - which is ~1 in 61 chance of that or worse happening - so no where near as improbable ... ~1 in 5 years.
March 19, 2016, 09:43:26 PM
hmm zachs page down for anyone? getting a 500 internal server error.
March 19, 2016, 09:25:47 PM
these crooks need to be punished!
is it true to assume, that the 46BTC that got away with were rightfully from other members?
thanks kano for being transparent in the matter.
Meanwhile, way to go frozencat!!! -- are you related to sabercatt, the block before you?
is it true to assume, that the 46BTC that got away with were rightfully from other members?
thanks kano for being transparent in the matter.
Meanwhile, way to go frozencat!!! -- are you related to sabercatt, the block before you?
Yea, nice job frozencat with your 13THs! I took the pooch for a walk and I missed this one
Edit: frozencat's block fell on shift lucy, the shift that has the least number of blocks...good girl lucy!
Jump to: