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

[gwk4]

I wonder if it is tied to the irregularity with the rewards level simultaneously dropping to 1/100 level

[Sixem]

you mean block #286209 on blockchain https://blockchain.info/nl/block-index/468084/000000000000000087e4e2f178c86c6802f0f22c83e00edc59eae7694fe92b59

last month i`ve seen the same problem with another pool where i have some miners, the pool operator said that blockchain isn`t always right
https://bitcointalk.org/index.php?topic=27062.msg4644357#msg4644357

[wdalessi]

286214 Sorry I typed the wrong block number. It's almost 12 hours now. It hates me. Hates me I saw.

[Sir Alan]

last month i`ve seen the same problem with another pool where i have some miners, the pool operator said that blockchain isn`t always right

Blockexplorer also links #286209 to Slush, and the payout address is correct on both Blockexplorer and Blockchain, so either they are both right or both wrong.

No doubt it will get fixed in due course.

[Mudbankkeith]

It must be time for the pool hoppers to go

[Sixem]

last month i`ve seen the same problem with another pool where i have some miners, the pool operator said that blockchain isn`t always right

Blockexplorer also links #286209 to Slush, and the payout address is correct on both Blockexplorer and Blockchain, so either they are both right or both wrong.

No doubt it will get fixed in due course.

it seems your right block #286126 (which slush`s solved) was payed to the same BTC adress as block #286209

[PostMixer]

last month i`ve seen the same problem with another pool where i have some miners, the pool operator said that blockchain isn`t always right

Blockexplorer also links #286209 to Slush, and the payout address is correct on both Blockexplorer and Blockchain, so either they are both right or both wrong.

No doubt it will get fixed in due course.

it seems your right block #286126 (which slush`s solved) was payed to the same BTC adress as block #286209

Have to agree with this….  https://blockchain.info/blocks/Slush

[Mudbankkeith]

last month i`ve seen the same problem with another pool where i have some miners, the pool operator said that blockchain isn`t always right

Blockexplorer also links #286209 to Slush, and the payout address is correct on both Blockexplorer and Blockchain, so either they are both right or both wrong.

No doubt it will get fixed in due course.

it seems your right block #286126 (which slush`s solved) was payed to the same BTC adress as block #286209

Have to agree with this….  https://blockchain.info/blocks/Slush

check your wallets guys n gals
a payment has just arrived in my wallet from slush, for the 10th,(still unconfirmed)
when I check back to the 10th I find the payment was already received, but the time stamp is different.

[KNK]

KNK,
I am not attempting to troll, far from it.  I have been with Slush consistently since Oct and run 200 GH/sec, quite satisfied to be here.  However, and to have an 86% luck for the pool over the chain growth of over 7000 blocks warrants consideration.  It is not just random noise related to small sample issues.  I have been reading erudite posts from OoC as well as others' with more or less rational explanations and denials of the trends.  Not being an IT professional I am merely suggesting that there might be a systematic advantage in the newly rising data centers' close proximity of the miners to one another that would give them an advantage, fewer stale shares being one.  I do believe that there might be room on this forum for intelligent discussion rather than either just cheerleading or flaming.

I am sure OoC can post stats for other pools having bad luck for even longer periods, because i remember there was a few months window of bad luck and longer blocks for some of the big pools (BTC Guild i think, but not sure).

Yes, your concerns about connection speed and delays are correct, but they cause different kind of problems for the pool, which is not the case right now. The fact that we had few rounds for a short time (21673 to 21679) means that the pool connections are fast enought to bring those blocks to the network in time.

It appears to me over time as Difficulty has risen and variance has followed the extreme blocks are getting longer and longer.  I remember when people freaked out over a 10 to 12 hour block. Now they defend it with honor. I am afraid when difficulty triples from where it is today. This will probably take a few days so not to be to concerned, the extreme blocks could easily extend for 24 hours or more.

I am curious. What is the shortest block time, and the longest block time anyone has ever seen here, and what the difficulty was at the time. I am not posting what I remember, but I remember some very fast, and very, very slow blocks, and am curious what others remember.

Not the Difficulty is causing the rounds to get longer, but the share we have from the entire network. Even if the difficulty goes down in half if the pool's hashrate is reduced to 1/3 at the same time we will still end with longer rounds.

[KNK]

Blockexplorer also links #286209 to Slush, and the payout address is correct on both Blockexplorer and Blockchain, so either they are both right or both wrong.

No doubt it will get fixed in due course.

it seems your right block #286126 (which slush`s solved) was payed to the same BTC adress as block #286209

Now, this is a valid point and I agree there is a problem with the pool, but I am also sure it will get fixed.

Maybe it will discover the problem for the last few weeks or maybe it's just temporary glitch, but is something that deserves attenion, not 'cheasing ghosts' like the complaints before.

[wdalessi]

I think at the end of the day people will be forced to use only the largest pools to reduce variance. Variance is the real problem that can be controlled. Difficulty is out of our control. The only other way is to mine PPS (Pay Per Share) and accept the higher pool fee's, as at least you know there is no variance. Just a higher pool fee. There are really very few options, and as time passes, the real options seem to be fewer and fewer.

[KNK]

The variance will always be there and with long periods of bad luck the PPS pools will have to close, so it won't fix the problems from variance, but merely move the impact from the miner to the pool (for a while).

Look at http://bitcoin.sipa.be/speed-lin-2k.png. Do you think 1/3 of the network simply disapears for a day - from 27PH down to 16PH several times on this graph only.

The network should find a block every 6 min regardless of the difficulty, but i remember blocks that took over 2h and that's no pool (even the largest one) had a block for 2+ hours. This equals to 20 times the difficulty shares from the entire network ... 20 is even out of the CDF chart on Slush

[wdalessi]

I understand what you are saying, but I feel if Difficulty was a constant that would help. If Difficulty continues to rise, and block times continue to get longer, you will solve fewer blocks over time before the difficulty increases. It is better to participate in as many blocks as possible in order to maximize earnings. For example you are in a small pool. It's a great pool. Your best friend and you run it. Because it is a small pool you only solve one (1) block per difficulty period. Every time you try to solve a new block the difficulty is 20% higher.

If you are in the largest pool run by Joe down the block. He started everything and has 90% of the total network hash rate. You solve a lot of blocks very fast, and get your share based on your hash rate.

If you and your buddies pool hits a bad streak and it takes 30 days to solve one block, difficulty has jumped 2 or 3 times.

In Joe's pool down the block, if he hits a bad spot it took him a couple extra minutes to solve the block.

Joe's pool still solves 1800 blocks before the difficulty goes up.

[gourmet]

The variance will always be there and with long periods of bad luck the PPS pools will have to close, so it won't fix the problems from variance, but merely move the impact from the miner to the pool (for a while).

Look at http://bitcoin.sipa.be/speed-lin-2k.png. Do you think 1/3 of the network simply disapears for a day - from 27PH down to 16PH several times on this graph only.

The network should find a block every 6 min regardless of the difficulty, but i remember blocks that took over 2h and that's no pool (even the largest one) had a block for 2+ hours. This equals to 20 times the difficulty shares from the entire network ... 20 is even out of the CDF chart on Slush

Normal block periode is 10 minutes, so 2 hours is only 12 times the difficulty.

[gollum]

I got less than 0.01 BTC in my account, how can I withdraw it all?

[wdalessi]

Keep mining till you get to .01
Set your payout for .01

If we get some fast blocks that will help.

Faster blocks are coming. But I can't tell you when.

[gourmet]

Why is the minimum payout so high.  My computer mines so slowly that it will take me months to reach the threshold.

Was the first sentence of your post intended to be a question?
(Hint: Questions end in a question-mark.)

[gollum]

Keep mining till you get to .01
Set your payout for .01

If we get some fast blocks that will help.

Faster blocks are coming. But I can't tell you when.

I wont mine ever again, it will be a loss for me. I just want my 0.001 out

[digdug111]

The web site just updated  and we are 3+ hours into the next block and the previous 11+ hours block has 75 verifications left.  Looks like the web site was having an update issue.  Hashing appears to have been working but the web stats were all messed up and the H/s still looks messed up.

[necro_nemesis]

I haven't witnessed that before, block 21687 showed up processing with 75 confirmations required and some 3 hours in.