[OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 #

[bulanula]

Uh oh.

DDoS. Working on it, should be back online soon.

Funny stuff. I remember you saying the other day Eligius would be harder to DDOS than P2Pool yet now I see p2pool still working.

I have nothing to do with the DDOS BTW. Just an observation and you got proved wrong ...

No, it didn't prove anything wrong. Eligius is still working, I just had to activate the DDoS protection - now we have more info to build on to automate activating it better next time. p2pool is still working because nobody bothered to try DDoSing it yet. If someone wanted to do a comparison to "prove me wrong", they need to DDoS p2pool too (which is just as illegal as DDoSing Eligius, so I don't endore doing it) with the same amount of bandwidth and see how each pool does after 24 hours of it.

Fair point. Did you find out why / who was DDOSing ? Called the FEDs ?

[1714795382]

1714795382

[Luke-Jr]

with the recently very poor luck, I'd be interested in how many blocks are we "behind". Is there some way to get info about negative buffer size? A graph would be cool (I like graphs), but numbers will suffice.

There is currently approximately 1000 BTC worth of extra credit issued.
Considering Eligius's history of above-average luck, and often peaking out over 1000 BTC buffered, this seems pretty normal/expected.
For comparison, another pool member noted yesterday that p2pool's luck works out to 2400 BTC behind.

If this goes on for too long, I might consider "upgrading" to ESMPPS just so new miners don't feel like they're losing out. Thoughts?

[The00Dustin]

I don't think you included a link in your post about going to ESMPPS pointing to information on the two systems.  This would make it easier for incredibly lazy bums who don't want to (or average joes who don't know where to) search for information on the difference between the two systems.

ETA: https://en.bitcoin.it/wiki/Comparison_of_mining_pools (and you thought I was one of those people)

This page links to Eligius's definition of SMPPS and a post about ESMPPS in a thread on this forum.  I guess I'd get paid the same amount at the end of the day, but with a low hashrate and more old work, I'm not sure which I like better.  I say we just get back to the other side of the luck.

[Luke-Jr]

http://eligius.st/wiki/index.php/Shared_Maximum_PPS also describes the variants.

[Krakonos]

I'm actually surprised it didn't come earlier.

If this goes on for too long, I might consider "upgrading" to ESMPPS just so new miners don't feel like they're losing out. Thoughts?

Would be pro. I already see the pool hashrate down. New people might help it a little.

[The00Dustin]

http://eligius.st/wiki/index.php/Shared_Maximum_PPS also describes the variants.

The link I posted links to that page, and I looked at it, but didn't scroll down.  Where's the facepalm emoticon?

[dunand]

We just finished a 23h57m round.

[rav3n_pl]

Something is odd there.
I point my miner to pool and after about 20hrs get stats:
http://eligius.st/~artefact2/7/1Q6igQVdYrxLKy5qJBXAEsSn91S1Zhnoii
Most strange thing is that miner shows:

Code:

(5s):105.5 (avg):146.2 Mh/s | Q:2795  A:176  R:1  HW:0  E:6%  U:0.16/m
TQ: 1  ST: 2  SS: 0  DW: 336  NB: 115  LW: 0  GF: 1  RF: 4

How is this possible that pool telling me that I have only about 10MH/s average???

[Luke-Jr]

Something is odd there.
I point my miner to pool and after about 20hrs get stats:
http://eligius.st/~artefact2/7/1Q6igQVdYrxLKy5qJBXAEsSn91S1Zhnoii
Most strange thing is that miner shows:

Code:

(5s):105.5 (avg):146.2 Mh/s | Q:2795  A:176  R:1  HW:0  E:6%  U:0.16/m
TQ: 1  ST: 2  SS: 0  DW: 336  NB: 115  LW: 0  GF: 1  RF: 4

How is this possible that pool telling me that I have only about 10MH/s average???

Do you have multiple pools defined in CGMiner? I think you need to set --failover-only or something or else it will "leak" work to secondary pools.

[Clipse]

Something is odd there.
I point my miner to pool and after about 20hrs get stats:
http://eligius.st/~artefact2/7/1Q6igQVdYrxLKy5qJBXAEsSn91S1Zhnoii
Most strange thing is that miner shows:

Code:

(5s):105.5 (avg):146.2 Mh/s | Q:2795  A:176  R:1  HW:0  E:6%  U:0.16/m
TQ: 1  ST: 2  SS: 0  DW: 336  NB: 115  LW: 0  GF: 1  RF: 4

How is this possible that pool telling me that I have only about 10MH/s average???

Your miner seems faulty , look at all the DW compared to Accepted shares , your U is far too low aswell at 100mh you should have a U of 1.397 and yours is 0.16 which means you are submitting shares to the pool at roughly 10-12mh and not 100mh.

Lastly, whats up with your efficiency? 6% ? All of this points to something faulty on your side unfortunately.

[rav3n_pl]

This is odd, it works fine on p2pool... Trying now BTCGuid and also have about 30MH/s reported on pool side and 150MH/s on miner side O_o

[stevegee58]

Something is odd there.
I point my miner to pool and after about 20hrs get stats:
http://eligius.st/~artefact2/7/1Q6igQVdYrxLKy5qJBXAEsSn91S1Zhnoii
Most strange thing is that miner shows:

Code:

(5s):105.5 (avg):146.2 Mh/s | Q:2795  A:176  R:1  HW:0  E:6%  U:0.16/m
TQ: 1  ST: 2  SS: 0  DW: 336  NB: 115  LW: 0  GF: 1  RF: 4

How is this possible that pool telling me that I have only about 10MH/s average???

Your miner seems faulty , look at all the DW compared to Accepted shares , your U is far too low aswell at 100mh you should have a U of 1.397 and yours is 0.16 which means you are submitting shares to the pool at roughly 10-12mh and not 100mh.

Lastly, whats up with your efficiency? 6% ? All of this points to something faulty on your side unfortunately.

The high discarded work ratio is characteristic of p2pool mining and is normal there.

[Clipse]

Something is odd there.
I point my miner to pool and after about 20hrs get stats:
http://eligius.st/~artefact2/7/1Q6igQVdYrxLKy5qJBXAEsSn91S1Zhnoii
Most strange thing is that miner shows:

Code:

(5s):105.5 (avg):146.2 Mh/s | Q:2795  A:176  R:1  HW:0  E:6%  U:0.16/m
TQ: 1  ST: 2  SS: 0  DW: 336  NB: 115  LW: 0  GF: 1  RF: 4

How is this possible that pool telling me that I have only about 10MH/s average???

Your miner seems faulty , look at all the DW compared to Accepted shares , your U is far too low aswell at 100mh you should have a U of 1.397 and yours is 0.16 which means you are submitting shares to the pool at roughly 10-12mh and not 100mh.

Lastly, whats up with your efficiency? 6% ? All of this points to something faulty on your side unfortunately.

The high discarded work ratio is characteristic of p2pool mining and is normal there.

Those are eligius mining results hench why I stated all those stats look like a faulty setup somewhere locally.

[Luke-Jr]

Pool is down hard. I think the datacenter must have a dead switch. Will post when I learn more.

[wizkid057]

Pool is down hard. I think the datacenter must have a dead switch. Will post when I learn more.

Discussed over with luke-jr and the few in #eligius.

Submitted shares are being directed at my temporary pool and going towards my "solo" mining efforts.

When the main Eligius server comes back online, I'll do a query to tally up the shares (being stored in a database) and do a sendmany at 100% PPS to everyone who submitted at least 1 share, whether or not any blocks are mined, out of my own funds.

I can sustain this for some time with or without any blocks at the current hash rate.  If need be, I will happily purchase the coins from Mtgox or #bitcoin-otc to make sure everyone is fairly paid and fulfill my promise.

I do have some stats scripts and such setup for monitoring my personal mining status, however they're all realtime and not really going to handle this amount of traffic, so, I'm going to be disabling them temporarily.  Once all is settled, I'll post a link where you can check your address against my database and you can verify that you get your deserved payout.

I've been hanging around on Freenode for some time, most of the #eligius regulars know me, etc.  I've also been helping behind the scenes with DoS mitigation for Eligius for some time now.  So, I hope this is a good solution to the temporary problem which everyone will be happy with.

Feel free to jump in the channel and ask away if you have any questions/comments/concerns.

-wk

[wizkid057]

Standard pool server is back online.

I have to get some sleep, but, first thing when I get home tomorrow (about 16 hours from the time of this post) and I get settled I'll be issuing payment, as promised, to everyone who continued to mine using my temporary setup.

I'll post the transaction id(s) here tomorrow after they're processed.

Happy mining!

[petabytecoin]

Standard pool server is back online.

I have to get some sleep, but, first thing when I get home tomorrow (about 16 hours from the time of this post) and I get settled I'll be issuing payment, as promised, to everyone who continued to mine using my temporary setup.

I'll post the transaction id(s) here tomorrow after they're processed.

Happy mining!

Thanks I had noticed the server problems soon after they started, was thinking about pointing my hashing power somewhere else, but your posts here put me at ease and I have kept hashing. Server stats are messed up but I'm confident you have your own records.

[muyuu]

I'm getting an "Unknown address" error.

[BCMan]

I'm getting an "Unknown address" error.

Yeah, same here. I hope mined bitcions are not lost. Waiting for my 0.5 btc >2 weeks already (haven't mined since then)!  

Unknown address !

Sorry man, I have no data for this address. Here is maybe why :

    There is a typo in your address. Make sure xxx is a valid Bitcoin address, and is yours !
    You just started mining. The stats usually show up a few minutes after the first submitted share.
    Your balance has been paid in full, and you are no longer mining.
    There is a problem with the API (very unlikely). If the problem persists, and you're aware of all all the text above, then join us on IRC for help (the link is at the bottom of the main page).

[The00Dustin]

I'm getting an "Unknown address" error.

Yeah, same here.

Me too, it's on artefact's script and even the sample address does it.