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

[Rikim4ru]

Just some salt on the bad luck xD

[Lucko]

Just some salt on the bad luck xD

You know that for sure or are you just guessing. 0.5% is normal, 8 to 9% is not...

[Rikim4ru]

 :PWow so close from another Orphan!!

Glad Slush won this one!

CHEERS!

https://blockchain.info/fr/block/000000000000000006d35d842f76f70bb5831f2e36337c03e61b837b48f14e5a

[Rikim4ru]

Jesus fucking christ.

Slush orphan rate is TERRIBLE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

With such bad luck for a 30ph pool, this is really unbelievable.

No really. You suck Slush!

https://blockchain.info/fr/block/000000000000000004d09e31247aa0efbba89cb35c146f96f7150d76c810d395

[Rikim4ru]

I.... Fucking give up.
Slush just scored another Orphan. Block 25170 Is found by Antpool. Slush fucked up again.
https://blockchain.info/block-index/00000000000000000b4153e7d0151f93a80ea128c6e478cdf4e52a56710953ec?site=slush



I rater point my rigs at Eligius... Imagine that.

[doubletap1911]

Does anyone see these Orphaned blocks as an attack by some of these Chinese Pools (specifically Antminer)?

[eleuthria]

Does anyone see these Orphaned blocks as an attack by some of these Chinese Pools (specifically Antminer)?

More likely it's just Slush's pool backend not updating to other blocks on the network fast enough (or being really slow in releasing its own blocks).  He's the only one having such absurd orphan rates, the problem is on his end.

[-ck]

Does anyone see these Orphaned blocks as an attack by some of these Chinese Pools (specifically Antminer)?

More likely it's just Slush's pool backend not updating to other blocks on the network fast enough (or being really slow in releasing its own blocks).  He's the only one having such absurd orphan rates, the problem is on his end.

Presumably everything has slowed down due to the extra load of having so much hashrate on his pool. Since slush's pool code is python, it's likely just the slowdown of python not scaling to the greater number of clients it's seeing. He either needs more mining nodes or better software.

From memory, slush's pool used to prioritise which clients got block updates first - since it takes time to send updates to all the miners, he prioritised the biggest miners first so all the small miners used to get the block change later. Perhaps even that workaround is no longer enough.

[OneInchWonder]

Im small time trying out this Bitcoin mining.
Suck to put in the hours and not get anything but shit happens.

[eleuthria]

Presumably everything has slowed down due to the extra load of having so much hashrate on his pool. Since slush's pool code is python, it's likely just the slowdown of python not scaling to the greater number of clients it's seeing. He either needs more mining nodes or better software.

From memory, slush's pool used to prioritise which clients got block updates first - since it takes time to send updates to all the miners, he prioritised the biggest miners first so all the small miners used to get the block change later. Perhaps even that workaround is no longer enough.

I'd assume something else is the issue.  I highly doubt he has more active miners than ever, just higher speed ones.  There's way fewer small fries out there today than there were a year or more ago.  In a proper implementation of vardiff, the speed of connected miners should have absolutely no impact on actual server load, only the number of miners in general.

[-ck]

Presumably everything has slowed down due to the extra load of having so much hashrate on his pool. Since slush's pool code is python, it's likely just the slowdown of python not scaling to the greater number of clients it's seeing. He either needs more mining nodes or better software.

From memory, slush's pool used to prioritise which clients got block updates first - since it takes time to send updates to all the miners, he prioritised the biggest miners first so all the small miners used to get the block change later. Perhaps even that workaround is no longer enough.

I'd assume something else is the issue.  I highly doubt he has more active miners than ever, just higher speed ones.  There's way fewer small fries out there today than there were a year or more ago.  In a proper implementation of vardiff, the speed of connected miners should have absolutely no impact on actual server load, only the number of miners in general.

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.

[doubletap1911]

In an email reply I received from Slush inquiring about the abnormally high invalid blocks he responded by stating "it was a matter of chance to end up with invalid block".  And additionally stating "We don't have direct impact over this behavior.  Invalid blocks are natural part of the Blockchain ecosystem..."

Do all of you agree with this?

[-ck]

In an email reply I received from Slush inquiring about the abnormally high invalid blocks he responded by stating "it was a matter of chance to end up with invalid block".  And additionally stating "We don't have direct impact over this behavior.  Invalid blocks are natural part of the Blockchain ecosystem..."

Do all of you agree with this?

It is an expected phenomenon of the way blocks propagate that orphans will eventually occur, but it is the responsibility of the pool owner to optimise their design to minimise this effect. Having orphans is expected, yes, but having a high rate of orphans is not expected. Check the orphan rates of other pools. The percentage should be about the same for all pools, irrespective of their size, though statistically it would be hard to get an accurate percentage on smaller pools simply because of the number of blocks solved.

[eleuthria]

In an email reply I received from Slush inquiring about the abnormally high invalid blocks he responded by stating "it was a matter of chance to end up with invalid block".  And additionally stating "We don't have direct impact over this behavior.  Invalid blocks are natural part of the Blockchain ecosystem..."

Do all of you agree with this?

There will always be *some* chance involved in orphan blocks.  But he's lyingdishonest in saying that you don't have direct impact over the behavior.  If your orphan rate is above ~1%, you have something wrong.


EDIT:  9 of his last 200 blocks have been orphaned.  There is CLEARLY something wrong with either the hardware, software, or network level for Slush.

[Rikim4ru]

Pool should be more reliable to this kind of issue...

For the last fews days we got really bad luck, combined with TOO MANY orphans.

I see a lot bad luck from slush but not so many lucky nowadays...  Maybe -Ck is right and they have a real network issue at this point.

With all the recent Dashboard issue and the 1.3 orphan per day rate... Something is wrong.

I wonder if Slush would ever compensate their top Miner  for this mess up... I Can't imagine running 1PH and not wanting to go straight to Slush HQ after LOSING more than 10BTC in revenue in the last week from invalidated block.

[Rikim4ru]

/Rant


I would really like slush to fix the Luck % right after an invalidated block...

80% for this day is not right. It's like 52% according to my (weak) math.

[OneInchWonder]

Block ID 25170 another invalid 

[Pyr3x]

I don't want to jump ship but I may have to do so...

[sky_g]

only 7 blocks yesterday.

Today only 3 blocks. Not good for users with very small hash power

[Rikim4ru]

Not good for huge hash power either!!!!!

IF AT LEAST those orphan were buried under a piles of Great Luck.... But it's quite the oppposite

I hope someone can Kick the box again and fix the luck  xD



Last 72 hours have been VERY terrible...
And the luck rating INCLUDE, all the past invalid block. So imagine that....

Still below 50% for 3 days straight.... For a 30 PH pool? BAH.