[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[Rikim4ru]

Up for another 9+hours Block?

-Sorry- I just can't believe how we can be hit by such bad luck. Consecutively.


Wtf.

[sky_g]

Up for another 9+hours Block?

-Sorry- I just can't believe how we can be hit by such bad luck. Consecutively.


Wtf.

3 invalid blocks in last 4 days toooooooooooooo

[spazzdla]

What is with the NMC stuff.. is the pool insta selling it and giving us the BTC?

[Rikim4ru]

What is with the NMC stuff.. is the pool insta selling it and giving us the BTC?

Yes.

They might implement nmc deposit soon, but right now it's the way it is.

[spazzdla]

What is with the NMC stuff.. is the pool insta selling it and giving us the BTC?

Yes.

They might implement nmc deposit soon, but right now it's the way it is.

Neato.

[doubletap1911]

I received another reply today from Slush regarding the recent influx of invalid blocks.

Thank you for pointing our attention to this situation. We understand your disappointment and are ready to provide you with more detailed explanation, please read below.

The primary reason for this behavior was recent malleability attack on Bitcoin network which caused the Bitcoind overload with transactions and directly affected the ability to propagate blocks into the network.
Not only our nodes were affected but many other nodes across entire BTC network as well.

Bitcoind 0.11.1 which was released 4 days ago contained bug fixes for these malleability attacks. We were testing it in the meantime in order to make sure we do will not cause any harm on our infrastructure and do not affect the
hash rate of our miners. We were stuck between a rock and a hard place these few days. But the unacceptable rise in number of invalid blocks forced us to act quickly. We would like to assure you that the new version of Bitcoind was successfully deployed on every node we use for our mining and blocks propagation. As a consequence we expect significant reduction in invalid blocks appearance in the next few days.

We hope you understand our struggle with the malleability attack and stay with us despite few bad days.
We are quick learners and are taking lessons from this experience which is going to have positive effect on your experience with our pool in the future

Martin
Customer support

SatoshiLabs
CoinMap | Slush's Pool | TREZOR

[-ck]

I received another reply today from Slush regarding the recent influx of invalid blocks.

The primary reason for this behavior was recent malleability attack on Bitcoin network which caused the Bitcoind overload with transactions and directly affected the ability to propagate blocks into the network.
Not only our nodes were affected but many other nodes across entire BTC network as well.

Which is what I said.

Well, probably that in combination with bitcoinds that haven't been optimised to cope in this transaction spam environment which can cause massive mempool and cpu blowouts and subsequently very slow block changes/getblocktemplate calls.

In other words slush hadn't manage to optimise his bitcoinds to cope under the circumstances and ended up depending on the newer bitcoind version to fix it. While he says many other nodes were affected, there were pools that were not.

[Pyr3x]

So now that he has applied this fix have things gotten any better?

[doubletap1911]

So now that he has applied this fix have things gotten any better?

No invalid blocks today and our luck looks like it is turning around as well.

[OneInchWonder]

So far so good last invalid block was on 2015-10-18 08:55

[Pyr3x]

So now that he has applied this fix have things gotten any better?

No invalid blocks today and our luck looks like it is turning around as well.

That is what I like to hear!

[Rikim4ru]

Speaked too fast  

https://blockchain.info/fr/block/0000000000000000014c463a40271798691071aba2c0d680403031bfdbcf0da3

3min42s late.....
WHAT KIND OF REFRESH RATE IS THIS.

What the hell!

[Rikim4ru]

That said.

I'm removing all my hashing from Slush.
Sorry, thought for sure you were one of the best pool!

But this is unacceptable.
Pay the fucking orphan, until then i'm out.

I won't be the stupid fuck that stay around in front of such a situation.

Slush at its current state is unreliable. Mine at your own risk? Dev won't share the risk with you that's for sure.

[lemmyK]

      o t i slush s pool..
Do something or go ......

[sky_g]

That said.

I'm removing all my hashing from Slush.
Sorry, thought for sure you were one of the best pool!

But this is unacceptable.
Pay the fucking orphan, until then i'm out.

I won't be the stupid fuck that stay around in front of such a situation.

Slush at its current state is unreliable. Mine at your own risk? Dev won't share the risk with you that's for sure.

I agree. i have only 12 TH pointing but it does not help me with orphan block found frequently.

[doubletap1911]

I'm going to hold on a bit longer before moving my hashing power to another pool.  Kinda ride out this turn of luck we have suddenly seen on Slush.  It can't be a coincidence that the day them fix the invalid blocks (supposedly fixed) that the luck turns totally around as well.  Had to be more going wrong behind the scenes than they are letting on.  Don't ya think??

[Pyr3x]

I'm going to hold on a bit longer before moving my hashing power to another pool.  Kinda ride out this turn of luck we have suddenly seen on Slush.  It can't be a coincidence that the day them fix the invalid blocks (supposedly fixed) that the luck turns totally around as well.  Had to be more going wrong behind the scenes than they are letting on.  Don't ya think??

So what are you saying he as ripping us off?

[doubletap1911]

I'm going to hold on a bit longer before moving my hashing power to another pool.  Kinda ride out this turn of luck we have suddenly seen on Slush.  It can't be a coincidence that the day them fix the invalid blocks (supposedly fixed) that the luck turns totally around as well.  Had to be more going wrong behind the scenes than they are letting on.  Don't ya think??

So what are you saying he as ripping us off?
[/quote

No, I'm not saying that.  But I do find it rather odd that the pool was not only having way too many invalid blocks but also the pool luck was sinking like a rock.  They supposedly fix the invalid issue and at the same time the pools luck does a complete 180.  I'm by no means a mining expert so I don't know if the reason for invalid blocks was also tanking our luck however I do know Slush does not report luck correctly when it comes to invalid blocks.  The pool luck should have been much lower if he was.  

I think the question as to whether or not he has been ripping us off should be answered by someone with a lot more mining knowledge then I.

EDIT:  However, case in point while having issues with invalid blocks we were seeing 4-6 hour rounds.  Now with the with the fix the rounds have been much much shorter except for the 4 hour one today which happens to be in invalid block (379375).  As a rule of thumb I don't believe in coincidences.  Don't get me wrong, I'm complaining about the good luck we have had these last two days. 

[doubletap1911]

Now it appears that block 379780 which at the time of me writing this we have been mining for 48 minutes was already mined by ant pool 22 minutes ago. This is a horrible delay on Slush's part, he needs to get this crap figured out quickly.

[Prelude]

Shouldn't a mod (-ck?) adjust this thread's title? The pool has been at ~32000TH/s for quite a while, now. 9000TH/s is old news.