I'd also be interested in this. Nobody seriously expects people to go to an office for IT anymore, do they?

Sorry, but Eligius has been noted as experimental from day 1, and the hardware issues made known as soon as we figured out what was going on, along with a recommendation to have a failover setup if you chose to continue mining on the failing hardware. Terrible luck as Ti had throughout this is also an unavoidable risk of mining.

Ti is still up on ghost.mining.eligius.st probably until Monday. There's a guy on IRC who has a bunch of supercomputer CPU miners that overloaded EU, and I want him to test on Ti to see how well the new software can handle it before unleashing it on Su. Once it's shutdown and the final block has 120 confirmations, I'll be sending any remaining balances via the usual sendmany.

Probability that we would find a block in that many shares. ie, 50% CDF = 50% chance we found a block by now

This does Proportional payouts, which are predictably unfair. To work, you'd have to also implement auto-hopping-- that is, when total shares reach 43%, throw them all away and start over. Alternatively, there is also a real-world PPLNS implementation in the Pools forum. Also, even with auto-hopping, each share would be valued at down to 0.00006806 at today's difficulty. Payouts of this size would result in huge transfer fees (which is why we added a minimum payout for Eligius) and coinbase transactions. Therefore, this kind of system would need to clutter together miners in different groups by similar hashpower so they all maintain at least 1% or so when the block is found. This also means that any number of CPU miners will still never find a block as a group.

I just deleted all of Eligius-Ti's DNS entries, following it finding a block. If you really want to keep mining on Ti, you must use ghost.mining.eligius.st-- but don't do that unless you have a lot of hashpower and are prepared to lose all the work if it crashes! Everyone should be on Eligius-Su now.

There has been some trouble with the new bitcoind, so please call me (whois eligi.us) IM me (luke ... dashjr.org) if any of the following occur:

• Pool isn't responding to work
• No longpolls notices even when the Bitcoin network has new blocks
• Estimates stop increasing as you get more shares

On the other hand, the new bitcoind has some improvements, including aggressive connecting to other nodes on the network which should hopefully eliminate invalid blocks.

If anyone would like to help work out these bugs, please meet me on IRC.

"Pool aggregation" is just making the pools a proxy to another pool (the "aggregator"). If you think it through, it makes little sense.

Please don't feed the troll just to promote your pool. The fact is that GimEEE's nonsensical rant against Eligius is not much different from his rant here. Eligius, also, announced the plans to transition to the new system about a month in advance. Eligius, also, will pay whatever BTC is owed. Etc.

We seem to be over the migration successfully. Eligius-Ti (aka Eligius-3) will be shutting down within the next 48 hours (possibly 24 hours) and given the usual sendmany payout. Please migrate your miners to Eligius-Su at your convenience (though if you choose to hold out for one last block on Ti, feel free). All DNS names are now pointed to Su except for Ti-specific names (s3, srv3, ti, cyan, 3). Once again, the recommended domain for mining is mining.eligius.st, and there is also test.mining.eligius.st if you prefer the most-experimental pool in the future.

Due to moving DB engines, all stats are now only available for the new Eligius-Su pool except for my raw JSON data.

If you have any trouble, please let us know on IRC!

Eligius is back up and running on new hardware (though website/stats are yet to be migrated)

Obviously, to have contests like this requires them to first take the money to buy the prize from the pool members in the form of a fee.
(Not saying it's bad, just pointing out the reality)

Do note that port 80 works on Eligius

Payouts are processed 50 BTC (+ txn fees) at a time, choosing the addresses which have been waiting the longest first. Since our last 3 blocks were rather long, the pool rewarded over 50 BTC per block, and there's a bit of a backlog. When we get to short blocks, it will catch up again.

Things are NOT back to normal. The machine has a failing hard drive. You can mine while it works, but at your own risk!

Every pool I've tried lately (BTCGuild, Bitcoins.lc, and of course Eligius) has had an occasional network error submitting blocks, even when it's not overloaded. Overload is pretty common during longpolls no matter how powerful the pool system, since it has to get new work for every single miner. What's the rationale behind giving up after one try, rather than giving it at least 5 minutes?
Perhaps it should be changed from a % to a simple decimal number? Or a hidden option to enable it? --I-know-what-efficiency-is

It uses too much system memory. In particular, I give my mining VM 256 MB RAM, and phatk just gets OOM-killed unless I add swap to it. If I go ahead and waste more RAM on it, I get a total of 1 MH/s improvement-- not worth it to me.

It keeps track of, and sorts by the age of the oldest unpaid coin. So whoever's been waiting the longest gets their payout first.

Thanks for the heads-up (in the future, IRC/phone is much faster to get my attention). I think I have a semi-fix for this issue for when we deploy 4 (on new hardware). In the meantime, 3 is caught up again. Shares were still counted as usual, and there were no negative side effects (though could have been if it went on too long).

• genjix started Spesmilo; I've just become one of the main developers
• Spesmilo website is: https://gitorious.org/bitcoin/spesmilo (we stopped using GitHub a long time ago)
• Spesmilo is licensed GPLv3

Thanks

Specifically, the total payout-if-this-were-PPS exceeded 50+64 (excess from past blocks) = 114 BTC.

I will disclose that there is presently a total of 311 BTC worth of rewards on Eligius-3 balances.

US/EU have been paid in full, and no longer have any balances to speak of. The final payout transaction from EU is still yet to appear in the block chain, but I have setup a bitcoind which has no purpose other than to rebroadcast it until it does-- at least Eligius-3 is willing to put it into a block. If anyone else wants to help us out in this crisis, the transaction id is 1c19389b0461f0901d8eace260764691926a5636c74bd8a3cc68db08dbbeb80a (you will need to addnode mining.eligius.st to see the broadcast)

Inevitably, it is a miner's choice where they mine. Hopefully people will reconsider when this is all resolved, given that the problems as of late were quite beyond anyone's control (hardware failure), and many people reported earning much more on Eligius than any other pool. On top of that, we do have some lucrative features, including Artefact2's very nice stats. Finally, please remember that Eligius still is, and always has been, clearly labeled as experimental, and I intend to leave it that way until I am personally comfortable with the long-term stability of the codebase.

EU was sent last Friday, and there's little I can do to get it confirmed with my measley 306 MH/s at this point. Eligius-3 is still online and looking for blocks. So long as it is online, the balances on it are still volatile and not really suitable for a final payout.

Any testing, no matter how little, is appreciated, and I will do my best to ensure gets rewarded properly.

Thanks for your patience. Hopefully this will all be behind us soon.