Topic: [350 GH/s] "Eligius" (experimental) pool: almost feeless PPS, hoppers welcome - page 20. (Read 116939 times)

I have shutdown the Europe pool temporarily and redirected its DNS to USA due to discovering a major bug (which accidentally never made it to the USA pool). I could use some help debugging it in #Eligius if anyone wants to volunteer some brainpower.

Edit: False alarm. Europe is and has been working properly. Pool brought back online.

uh, how cool is that! Thanks for the hint. No more fiddling around with the "flexible pool proxy"

@Luke-Jr

Hi! I just wanted to extend a note of gratitude for the efforts of yourself and your collaborators on the Eligius pool. You've done well bootstrapping this thing and it appears to be polishing up and gaining support nicely.

I'm still relatively new to the pooled mining scene, having just a few weeks ago stopped generating on my own.

I scoured this forum and other resources learning about the pooled mining scene and evaluating the pools to decide which I should join. Bitcoinpool had really looked the most interesting to me, and I was just about to set up there when they experienced their April security breach, leading to a number of accounts being compromised and having their payment streams redirected.

I think they are doing their best at bitcoinpool, but after watching them for a few weeks now, I still have reservations that they may they have architected the accounts system in a way that leaves it fatally vulnerable.

My guess here, some posts to their forum suggest they (had been, and if true maybe are still) are storing actual account passwords in their database, rather than salted hashes. One post suggested the attacker got hold of the accounts database, and was using the raw passwords stored therein to begin redirecting the payment streams; something that the best practice of using salted hashes would have prevented, if that was in fact what transpired. The website itself, where accounts are created and managed, has no security, and they appear to me (disturbingly) to eschew the basic value of securing account/registration sessions with SSL. Little niggles of this sort suggest they may have an incomplete understanding of robust security practices.

So then I see this very forum topic!

What a concept! Forget the account. Just point your miner at our server, mine away, and just tell us the bitcoin address where you want the credit sent. This is so brilliant it seems like one of those obvious things you wonder how no one thought about it sooner?

In the aftermath of their breach, I mentioned the Eligius approach on the bitcoinpool forum as an idea about shortcutting the inherent need to start carefully considering security once accounts come into play. The responses were skeptical; along the line that this would make it hard to trust the pool operator, because it would be difficult to verify that your work was being properly credited.

I admit to being ignorant about the mechanics of the various pooled mining credit systems, but at least I have been able to observe the diligent efforts you've put forth making Eligius completely up-front and transparent. You've proven that even without accounts, self-auditing and tracking is possible.

With the polish starting to shine on this pool, it's feeling less experimental now. But the novel feature of an accountless architecture has made ME feel safer testing and now fully adopting it for my use, than the other more well established pools available. So, thanks! I'm sure I cannot be the only one who feels like this.

In case anyone hasn't noticed yet, we have a growing community at #Eligius (FreeNode) and http://eligius.st (email me for your own webspace)

Some various change-ideas are being discussed on IRC, and I would appreciate participation from everyone/anyone that uses the pool and wishes to have a say on what changes get made.

US pool is rocking it today. Come on big money!

EU pool is working fine, it almost feels a bit like solo mining though

The only issue there is that if you have multiple machines in multiple locations with multiple gpu's, all oc'ed to a stable max, i really like to get an email if something happens, i.e. some connction issue or if i need to nudge the clock down a bit on a card since a driver crashed. email gives me that with workers set up for each gpu.
I really like your system and generated coin transactions but i need that backup warning system. Such complexity is totally against the logic of your pool hence i use btcmine as backup "email warning" pool. Dont get me wrong, its all good the way its simple and how u now have that nice statspage, its just that beyond a number of gpu some sort of monitoring is required.
If i ran 3 gpu i would also do the eu main us failover setup

Right, preferably your local Eligius is the main instance, and the other Eligius can be your backup pool

you should run 1 main instance and one to a "backup pool", preferably not the same pool.

i use my main mining now at eu eligius and the failover are btcmine. if this goes down btcmine takes over, if btcmine is down i get an email :p

Also, for any noobs to Bitcoin like me, just realised, I can set my miners to two different servers one with a lower aggression level so when one server goes down, it just picks up on the other.

At the moment I have my cards pointed at the eu server with aggression 13 - but also another 2 instances of Pheonix miner running pointing to the US server with aggression 4 - works too

Wish id known that before!

Luke thanks so much! So basically I don't get paid till I find a block correct? A block is worth how much? Like 1 BTC? I know this probably isn't the place to be asking this, but I just looked into getting rid of my GTX 285 and upgrading to a Radeon 5870. Looks like this item is basically not being produced anymore? Is that correct? So my best chances are finding it used? I really wanna get a good rig started to start saving for a new rig! I cant wait to hit the Ghash/s range!!

Luke while your replying, you might want to change the front page for the correct servers? in case people are trying to join but cant

A stale block occurs when two miners find the same block at basically the same time. Due to the design of Bitcoin, only one of them can be the "real" block. Until the next block is found, they continue to compete by the miners who are looking for the next block; when the next block is found, the one it chose to be based on becomes the real block, and the other one becomes an orphan. At that time, it basically ceases to exist retroactively.

When Eligius has a stale block, it works the same way: it ceases to exist. Payouts in that block (usually rewards for the same block) cease to exist. Your shares are counted toward the next block, just as if the stale one was never found, so they will be paid when the pool finds its next block.

Stale blocks should not be confused with stale shares, which is what your mining program might report. A stale share occurs when the pool has already moved on to the next block, yet your miner is still submitting shares against the last block. Eligius supports long polling, so it can tell miners immediately when it moves on to a new block. Therefore, if your miner continues to submit stale shares, they are rejected as invalid and not counted toward your earnings.

Quick question. When you get a stale/invalid do you still get paid for that, and what is an invalid/stale anyway?

well, back on your service and bumping it a bit #1 already

The pools are most certainly up far far more than they are down. I am pretty sure total combined downtime combined has been under 24 hours since I started Eligius.

Total time that both have been down at the same time, I believe, is never (since starting Europe). I personally run two miners, one on each pool, so that when one goes down the other picks up the slack.

Unfortunately, most of the downtime has been from pushpool bugs under high load, which are extremely difficult to debug without a high-load test server. And with only 40-50 GH total, I'm not certain there's enough people yet willing to run on a "guinea-pig" debugging server? If there is, I could probably set one up... As things are, I've just been killing and restarting pushpool when it goes bad in an attempt to get things back online ASAP.

Also, Artefact2's pool statistics seem to be having an issue graphing the pool hashrates; the majority of the missing spots on the graph are not downtime at all.

Correction: sorry for not double-checking, my fixed balance seems to have dropped to zero quite correctly now, and the beginning of the drop is actually quite visible at the end of the above graphs...

...however, it appears fairly certain that during block 126448 (23:30 on Tuesday, April 24 UTC), that did not happen on graphs.

Yeah, downtime is a nuisance, good luck with getting the system stabilized! And thanks for creating this pool, having a multitude of smaller pools helps make BitCoin safer, so I'm happy to see a new one, and joined!

I have a potential bug or inconsistency to report, though.

I mined on the US server. Rest assured, I received my payout from the last two blocks perfectly fine (my address is the one which received 1.21274402 BTC with block 126610 and 1.09924254 BTC with block 126448.

However, the graphs displayed by Artefact2 seem to contradict this, leaving the impression that I've not received my payout, when I actually have. Should the "fixed balance" area, painted green, not drop to zero on payout? It seems to have done that a few days ago on Sunday, but no longer does... or am I misunderstanding it, and it should not always do that?

Snapshot from right before the last block was generated:


Snapshot from right after the last block was generated:

The luck is irrelevant, but the downtimes are starting to get a bit too frequent for my taste. I'll give this pool one week at most and then I have to abandon it if the uptimes aren't counted in days instead of hours...

I like the pool a lot though so I hope the uptimes will get better.

Your not making this an easy choice to stay with you with the constant downtime, I like the server, but it just gets a little silly with the downtime combined with bad luck (luck not your fault obviously)