Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB

[Todamont]

I'm just noticing that over the last 3 days, I've only made approximately 30% of my expected returns, and it seems to be just bad luck from this pool. That's some serious, sustained bad luck.

[1714250357]

1714250357

[1714250357]

1714250357

[1714250357]

1714250357

[1714250357]

1714250357

[1714250357]

1714250357

[mdude77]

I'm just noticing that over the last 3 days, I've only made approximately 30% of my expected returns, and it seems to be just bad luck from this pool. That's some serious, sustained bad luck.

According to my math:

last 10 blocks: 151%
last 12 hours: 125%
last 24 hours: 89%
last 7 days: 74%

M

[Todamont]

>> maintaining your 3-hour average hash rate of 218.87 Gh/s is 0.02198455 BTC per day.

>> Latest Payout: 2014-03-28 08:41:50

>> Estimated Total: 0.02323145 (as of 2014-04-02 01:36:00)

So I should have made like 0.065 but I made 0.023 instead in the last three days.

EDIT: sorry glitch in the stats wasn't showing the last actual payout, which was on the 31st, so I'm fine with the pool. Thx

[lightfoot]

Good reason to split hashing between pools, eclipse had a pair of ball busters: 2 days of hashing with 600gh for what: 2 cents? :-)

Luck will stabilize out. However as difficulty goes up we *will* see more variance.

C

[GigaWave]

Just want to note that Eligius has been under constant DDoS attacks for well over a week now.  Mitigation sometimes requires temporarily killing one or more public facing IPs and letting miners reconnect to others.  As long as you're using the proper hostname, stratum.mining.eligius.st, then your miners should do all of this automatically.

Any hypothesis as to why?

Has it contributed to the bad luck at all? The payment queue is quite long.
 

[Lucko]

Okay, I see some wonkiness took place last night for a few others, but not many.

My stats were just a bit off (not an issue, could be latency), but there was a stat/issue that was troubling. My KnC (moved to the stadard port after FW update by WK's writ!) just dropped out of the pool. No failover. Hashrate dropped from 143 GH/s to ~800 MH/s. Tried to get it going, and no dice.

My BFL units still showed they were hashing, but the stats for that ~175 GH/s dropped out, too. All that was showing was ~70 GH/s from my TechnoBit miners.

This was at around 2 am CST, I want to say, but can't be exact, unfortunately. BFGminer showed that the BFL units were hashing again at Eligius, but stats still didn't reflect this. This was an hour ago when I tried again... or was able to try again. I'm sure it was hshing, as I saw a bit of buildup in shares, so it seems the hashrate stat was mainly affected.

I've mainly just stuck to the pool despite stats, but when a miner drops the pool and won't reconnect, I decided to switch. I've taken my small op to another pool for the next hours until I hear more feedback from the pool. If all is kosher again, I'll try to move the KnC. If it will connect to the pool, I'll be good. As mentioned, I don't worry about the stats as long as I can see shares being processed. That stopped for both my BFL units (using bfgminer) and the KnC (also bfgminer). maybe just a fluke on my end with the BFL units. I just had to rebuild my system, and it's buggy. Doesn't explain the KnC instance, nor why the TechnoBit units still showed in my stats. Just odd. I've read the rest of the thread from the days I was out of commission, and noticed all the posts regarding DDoS, but didn't think it would affect the pool, nor do I still think it necessarily would. I might attribute the oddness I saw in the stats page to that, but the rest is odd. I've witnessed the network drop before, where I couldn't access Eligius nor two failovers - switched to PPC for a few hours - but this was isolated to Eligius, as far as I could tell. I had forgotten my BTCguild account and made a new one last night and connected right away. I'm there for now (until I can build up a small payout, and then try Eligius again).

Anyone else notice anything remotely similar? Just trying to figure out what might be on my end, what's up with the KnC, and why the TechnoBits never fell. lol - No panicking, just curious if anyone noticed the same issues, and if they somehow resolved them. Hope to switch back later. Just upped my donation, but guess I wasn't quick enough. lol jk  Again, some of this may be on my end. I've had a lot of issues getting the BFL units working properly after rebuilding y system, and my KnC has been wonky off-and-on for a few weeks. You know, the usual.

I seen same thing but on TechnoBits units. It went from 1TH to almost zero. but my total heshrate was constant. It looks like shares were not credited to worker but to my general address only. No idea why this happen. Switching off and then back on the pool solved that.

[Lucko]

Yes luck is down... Number is estimate not what you will get. Long term average will be that but there will be days you will see much more or much less...

[pedrosoft]

>> maintaining your 3-hour average hash rate of 218.87 Gh/s is 0.02198455 BTC per day.

>> Latest Payout: 2014-03-28 08:41:50

>> Estimated Total: 0.02323145 (as of 2014-04-02 01:36:00)

So I should have made like 0.065 but I made 0.023 instead in the last three days.

yes, I met the same problem.

everyone please check your account. The payment is wrong!!!

Just check your income. 25%-30% is missing. Is there something wrong?

I've changed pool. Eligius has very very low hashrate 40 % less than normal. On ghash.io all my miners are working fine

[Lucko]

Go to blockchain.info and see how many blocks do Eligius find. You will see it is only that... It happened the same on BTCGuild. 90 days average was 87%... It happens...

EDIT: Numbers from there: Approximate Pool Luck* (24H / 3D / 1W / 2W / 1M / 3M / 6M): 82.260% / 89.902% / 91.992% / 88.882% / 89.889% / 97.229% / 100.716%

So if you would be at BTCGuld you would last 2 weeks only got 89% and last month 90%... - 3% fee... And 2 days back thus numbers were much lower... It looks like new privet mining operations have good luck since all public pools have bad...

[Lucko]

How could 90 days of 87% happened? It just happens.

Everyone has the same income. My is also about 75%...

If you don't trust pool operator the only thing you can do is change the pool. But at current difficulty/hashrate it is hard to say that anything is wrong at the moment.

[wizkid057]

Luck is luck.  Stop trying to spread FUD.  Everything is accounted for here, and there is next to zero trust needed here as everything is verifiable.  You can look look at your own traffic and see that every share you submit hashes 'Eligius' into the block's coinbase.  Feel free to do your own scan of the blockchain.

Also, DDoS attacks have had no impact on luck, nor can they possibly have any impact on luck.  Again, luck is luck.  I don't see anyone complain when we have days/weeks where we're well over average luck... which is just as probable.

Deleted posts from newbie account trying to spread nonsense, deliberately removing the word 'estimated' from stats copy/pastes, and generally having no clue what they were talking about.
Leaving others who quoted alone, but please don't feed the trolls further.

[hot_gpu]

Once a day my commute miner against another pool because the failover is activated.

Is there a problem in the pool for users with KNC?

then connect with stratum.mining.eligius.st: 3334?

Thx in advance!

[wizkid057]

Once a day my commute miner against another pool because the failover is activated.

Is there a problem in the pool for users with KNC?

then connect with stratum.mining.eligius.st: 3334?

Thx in advance!

Most likely shuffling of resources on this end due to DDoS attacks causing you to need to reconnect occasionally.

[baddw]

Once a day my commute miner against another pool because the failover is activated.

Is there a problem in the pool for users with KNC?

then connect with stratum.mining.eligius.st: 3334?

Thx in advance!

Most likely shuffling of resources on this end due to DDoS attacks causing you to need to reconnect occasionally.

Could it be that the calculated luck numbers are being skewed by the people having connectivity problems?  If the pool has a certain TH/s, then (say) 10% of those people drop connections for an hour, how long does it take for the pool to re-calculate its expected block rate?  I assume it uses the 3-hour rolling average, but if the round starts when everybody is connected, wouldn't the luck calculation be set at that time, and not change until the next round?  Of course, the opposite would also be true, and push the luck upwards temporarily, but adding hashrate makes blocks be found quicker, thus resetting the luck calculation faster.

[wizkid057]

Once a day my commute miner against another pool because the failover is activated.

Is there a problem in the pool for users with KNC?

then connect with stratum.mining.eligius.st: 3334?

Thx in advance!

Most likely shuffling of resources on this end due to DDoS attacks causing you to need to reconnect occasionally.

Could it be that the calculated luck numbers are being skewed by the people having connectivity problems?  If the pool has a certain TH/s, then (say) 10% of those people drop connections for an hour, how long does it take for the pool to re-calculate its expected block rate?  I assume it uses the 3-hour rolling average, but if the round starts when everybody is connected, wouldn't the luck calculation be set at that time, and not change until the next round?  Of course, the opposite would also be true, and push the luck upwards temporarily, but adding hashrate makes blocks be found quicker, thus resetting the luck calculation faster.

Luck has no relation to how many people are connected,  disconnected,  reconnecting,  whatever. It is a stat that has no real meaning whatsoever and is there as fun information. It is calculated based on difficulty and accepted shares for the round.

If a miner is disconnected they have no shares being accepted and thus are not factored into the calculations.

[gallery2000]

Would praying to Zeus change our luck?

Luck is luck.  Stop trying to spread FUD.  Everything is accounted for here, and there is next to zero trust needed here as everything is verifiable.  You can look look at your own traffic and see that every share you submit hashes 'Eligius' into the block's coinbase.  Feel free to do your own scan of the blockchain.

Also, DDoS attacks have had no impact on luck, nor can they possibly have any impact on luck.  Again, luck is luck.  I don't see anyone complain when we have days/weeks where we're well over average luck... which is just as probable.

Deleted posts from newbie account trying to spread nonsense, deliberately removing the word 'estimated' from stats copy/pastes, and generally having no clue what they were talking about.
Leaving others who quoted alone, but please don't feed the trolls further.

[wizkid057]

Would praying to Zeus change our luck?

Has about as much of a chance as the DDoS attacks: zero.

[gallery2000]

That's what I suspected.

Would praying to Zeus change our luck?

Has about as much of a chance as the DDoS attacks: zero.

[baddw]

Luck has no relation to how many people are connected,  disconnected,  reconnecting,  whatever. It is a stat that has no real meaning whatsoever and is there as fun information. It is calculated based on difficulty and accepted shares for the round.

If a miner is disconnected they have no shares being accepted and thus are not factored into the calculations.

Oh!  Of course!  Sorry, I forgot how simple the luck calculation actually is.  That's what I get for posting without having any caffeine...

[bolverk]

Just want to note that Eligius has been under constant DDoS attacks for well over a week now.  Mitigation sometimes requires temporarily killing one or more public facing IPs and letting miners reconnect to others.  As long as you're using the proper hostname, stratum.mining.eligius.st, then your miners should do all of this automatically.

What a ball-ache wk - how can you mitigate against this kind of anal attack... More servers is all I can think of... Keep up the good effort!

Mitigating DDoS attacks is pretty basic, depending on whether they're trying to attack the TCP stack (like SYN floods) or the protocol (like that NTP reflection attack that was going on a couple of months ago).  More servers won't help unless you have a genuine scaling problem.