Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 76. (Read 4382653 times)
February 08, 2016, 03:48:48 PM
not happy
February 08, 2016, 03:19:33 PM
Yeah in hindsight now and thinking about this more clearly something really stinks about this explanation from Slush. He is really not coming clean at all here.
For months we have been watching this cycle and have made repeated attempts to communicate this pattern to him for explanation. Nothing. Now he is basically saying that this particular miner was "accidentally" withholding blocks and that the problem has been fixed...and in fact he knows it has been fixed as that same miner has since the repair cracked two blocks... just not right and not near enough.
Slush should have banned that miner immediately (there must be a way to do this) and made an attempt to recover lost funds to return to those of us who stuck with him for so long. I have been gone from Slush for a few weeks now (actually stopped mining all together as there is no suitable outlet for a small scale miner like me anymore), Slush has definitely soured me on BTC mining as a result though.
Really rotten.
For months we have been watching this cycle and have made repeated attempts to communicate this pattern to him for explanation. Nothing. Now he is basically saying that this particular miner was "accidentally" withholding blocks and that the problem has been fixed...and in fact he knows it has been fixed as that same miner has since the repair cracked two blocks... just not right and not near enough.
Slush should have banned that miner immediately (there must be a way to do this) and made an attempt to recover lost funds to return to those of us who stuck with him for so long. I have been gone from Slush for a few weeks now (actually stopped mining all together as there is no suitable outlet for a small scale miner like me anymore), Slush has definitely soured me on BTC mining as a result though.
Really rotten.
February 08, 2016, 03:01:16 PM
I mean I have only been mining since the end of December, and right away I knew something was up. I thought to myself, how can 40ph find only one block a day when at the time you had 4ph pools average 1.2 blocks a day. After about 3 weeks on slush pool I noticed this and pulled out and haven't looked back. I am frankly amazed people are still mining on this pool.
February 08, 2016, 02:41:42 PM
Slush is not coming clean. Far from it. This issue was known about for weeks and the answer was always bad luck. They knew there was an issue and did not do the right thing and inform their loyal miners that they could be subject to lose a lot of revenue. MONTHS
I lost many BTC from this debacle and they have refused any compensation.
I lost many BTC from this debacle and they have refused any compensation.
Best Regards
d57heinz
February 08, 2016, 01:38:33 PM
Slush is not coming clean. Far from it. This issue was known about for weeks and the answer was always bad luck. They knew there was an issue and did not do the right thing and inform their loyal miners that they could be subject to lose a lot of revenue.
I lost many BTC from this debacle and they have refused any compensation.
I lost many BTC from this debacle and they have refused any compensation.
February 08, 2016, 12:23:54 PM
just wasted 4 Ph with incredible bad luck , 2 blocks > 23 h
3.80 btc loss =) hihaaaaa
3.80 btc loss =) hihaaaaa
February 08, 2016, 08:35:15 AM
Good to see Slush is trying to come clean, but of course the damage is done and I think it will take much for him to rebuild trust; agree there needs to be more disclosure on who this miner was and what/how the block withholding attack was accomplished.
February 08, 2016, 08:19:01 AM
Well, the correct action would be to deduct the rewards paid to a miner who was withholding, and distribute them to the miners who were not paid what they should have been ...
It doesn't matter if it was accidental or not, the miner caused it and received payments that they should not have, and should have gone to the other miners.
The miners here should also be aware that for a pool to detect, with marginal certainly, that a miner is withholding, the miner would have had to mine more than the equivalent of 10 blocks and failed to find any blocks.It doesn't matter if it was accidental or not, the miner caused it and received payments that they should not have, and should have gone to the other miners.
i.e. the miner would have been paid over 250BTC, while withholding, probably a lot more, that needs to be returned to the pool and distributed to the other miners.
I suggest you bring this up with the pool operator, since he was underpaying everyone by giving BTC to someone who was block withholding and he should be taking it back from them and returning it to the rest of the miners.
Also he should provide the bitcoin community with the details of what the miner was and the modifications made, to help stop it happening anywhere else ... unless he doesn't care?
--
I've sent [email protected] an email saying they need to deal with this properly and a link to this post.
lets hope he does pay us some sort of compo lol or hes gonna lose a lot oif unhappy miners
February 08, 2016, 04:38:24 AM
Well, the correct action would be to deduct the rewards paid to a miner who was withholding, and distribute them to the miners who were not paid what they should have been ...
It doesn't matter if it was accidental or not, the miner caused it and received payments that they should not have, and should have gone to the other miners.
The miners here should also be aware that for a pool to detect, with marginal certainly, that a miner is withholding, the miner would have had to mine more than the equivalent of 10 blocks and failed to find any blocks.It doesn't matter if it was accidental or not, the miner caused it and received payments that they should not have, and should have gone to the other miners.
i.e. the miner would have been paid over 250BTC, while withholding, probably a lot more, that needs to be returned to the pool and distributed to the other miners.
I suggest you bring this up with the pool operator, since he was underpaying everyone by giving BTC to someone who was block withholding and he should be taking it back from them and returning it to the rest of the miners.
Also he should provide the bitcoin community with the details of what the miner was and the modifications made, to help stop it happening anywhere else ... unless he doesn't care?
--
I've sent [email protected] an email saying they need to deal with this properly and a link to this post.
AS i have aswell.. on their facebook page since that is the only place they check for support related shit.. I know crazy right!?? anyway we will see whats up since we were on slush about this since back at least as far as november 2015 from what ive seen posted on fb. Looking forward to see how this is handled!
Best Regards
d57heinz
February 08, 2016, 12:42:02 AM
Well, the correct action would be to deduct the rewards paid to a miner who was withholding, and distribute them to the miners who were not paid what they should have been ...
It doesn't matter if it was accidental or not, the miner caused it and received payments that they should not have, and should have gone to the other miners.
The miners here should also be aware that for a pool to detect, with marginal certainly, that a miner is withholding, the miner would have had to mine more than the equivalent of 10 blocks and failed to find any blocks.It doesn't matter if it was accidental or not, the miner caused it and received payments that they should not have, and should have gone to the other miners.
i.e. the miner would have been paid over 250BTC, while withholding, probably a lot more, that needs to be returned to the pool and distributed to the other miners.
I suggest you bring this up with the pool operator, since he was underpaying everyone by giving BTC to someone who was block withholding and he should be taking it back from them and returning it to the rest of the miners.
Also he should provide the bitcoin community with the details of what the miner was and the modifications made, to help stop it happening anywhere else ... unless he doesn't care?
--
I've sent [email protected] an email saying they need to deal with this properly and a link to this post.
February 07, 2016, 10:16:49 PM
Since nobody's posted it yet this is the announcement page of the block-withholding.
https://mining.bitcoin.cz/news/recent-low-luck-information/
https://mining.bitcoin.cz/news/recent-low-luck-information/
February 07, 2016, 10:16:34 PM
he posted this
Dear miners,
we would like to inform you that we have detected and resolved an unintentional block withholding attack.
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved.
A recent time period of worse luck can be at least partly attributed to this incident.
Block withholding attack is a well-known weakness of the whole pool mining principle and no public pool is immune against it.
As a by-product of the bad luck investigation, we have implemented a new method how to mathematically prove that the pool does not cheat on miners. This feature will be released after the public interface has been tweaked. The release is planned towards the end of next week.
Dear miners,
we would like to inform you that we have detected and resolved an unintentional block withholding attack.
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved.
A recent time period of worse luck can be at least partly attributed to this incident.
Block withholding attack is a well-known weakness of the whole pool mining principle and no public pool is immune against it.
As a by-product of the bad luck investigation, we have implemented a new method how to mathematically prove that the pool does not cheat on miners. This feature will be released after the public interface has been tweaked. The release is planned towards the end of next week.
The correct thing to do is to simply inform the public:
(1) What is the make and model of the miner?
(2) What is the version of the custom firmware?
(3) How to detect such "rogue" miners?
Why did the pool operator not release such public service announcement?
February 07, 2016, 09:53:43 PM
This reeks of bullshit.
February 07, 2016, 07:07:50 PM
That message is just full of shit. Yea right miner was makeing problems.
February 07, 2016, 05:17:16 PM
Come on, does anyone really believe it was a "random" miner?
February 07, 2016, 04:53:48 PM
Well, the correct action would be to deduct the rewards paid to a miner who was withholding, and distribute them to the miners who were not paid what they should have been ...
It doesn't matter if it was accidental or not, the miner caused it and received payments that they should not have, and should have gone to the other miners.
It doesn't matter if it was accidental or not, the miner caused it and received payments that they should not have, and should have gone to the other miners.
February 07, 2016, 10:29:47 AM
Good job sir 
. lets go slush pool
. lets go slush pool February 07, 2016, 08:13:41 AM
he posted this
Dear miners,
we would like to inform you that we have detected and resolved an unintentional block withholding attack.
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved.
A recent time period of worse luck can be at least partly attributed to this incident.
Block withholding attack is a well-known weakness of the whole pool mining principle and no public pool is immune against it.
As a by-product of the bad luck investigation, we have implemented a new method how to mathematically prove that the pool does not cheat on miners. This feature will be released after the public interface has been tweaked. The release is planned towards the end of next week.
Dear miners,
we would like to inform you that we have detected and resolved an unintentional block withholding attack.
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved.
A recent time period of worse luck can be at least partly attributed to this incident.
Block withholding attack is a well-known weakness of the whole pool mining principle and no public pool is immune against it.
As a by-product of the bad luck investigation, we have implemented a new method how to mathematically prove that the pool does not cheat on miners. This feature will be released after the public interface has been tweaked. The release is planned towards the end of next week.
February 07, 2016, 07:01:26 AM
Yea they fixed it now and adding something extra I seen on his Facebook
February 06, 2016, 12:46:39 PM
many blocks solved today
Jump to: