IMO, 10 BTC is a pitiful amount for a business application.

I would be neat if you had a way that they could opt to download and run a miner in a pool (Eligius would be a perfect fit since it can payout to any address without registration) and mine enough to pay the access charge...

No, I said I wrote the core code for Eligius. Pushpool is only one part of a pool, it is not the whole pool.

Without a block, there is no bitcoin to get.

Yep, Europe has only found 4 blocks so far.

Nonsense, I was on IRC all day, as many others can attest. You disappeared shortly after the agreement, and didn't re-appear on IRC until yesterday.
No, I do not agree. If you had been there, the trade would have been executed as planned: you would have gained $28.75 ($5.50 profit over market price) and I would have gained 25 BTC.
No, by demanding the difference from me, you are in effect demanding I not only buy at $1.15, but also sell back to you at $0.8x.

The fact is, you lost $5.50 because you broke the deal and never showed up. I lost $193.75 because you broke the deal. If anything, you owe me since you broke the deal.

Facts:

• On April 13, the price fluxuated between 0.92 and 0.93 USD.
• Significant portions of the log are omitted in the paste above
• After fumbling around with technical details (escrow topics, etc), we decided to avoid the complexity and:
• We agreed that I would purchase 25 BTC at the price of 1.15 USD from him on April 13th, with our word at stake
• He never showed on April 13, up until today, May 17
• I am still willing to buy 25 BTC at the price of 1.15 USD
• I was never under any obligation to sell the 25 BTC back, at any time
• Had he showed on April 13th, I would have completed the sale then, and held onto the 25 BTC until I could sell it at 8.90 USD, making a significant profit
• (edit-added) blarzong last appeared on IRC on March 15th

It is in fact "ruhvix" who is the scammer at this point.

Everything under http://eligius.st/~luke-jr/ should be more or less working. Webspace available for Eligius-related projects on the server. Read-only access to the MySQL database is included.

Awesome idea.

I'd probably use Postgres if I knew it. But MySQL has phpMyAdmin, so... I did consider switching anyway when the MySQL people told me I couldn't do replication that wasn't 1:1, but then the Postgres people said the same thing.

Stats are being moved to http://eligius.st/~luke-jr/raw/ but it isn't done yet.

US MySQL is taking forever to add an id column. Europe should be fine in the meantime.

Since it's been a while since my last update, I just wanted to say that I am working on improving stability. At the same time, I am also working on some new features including a server in Europe for Eligius. It is currently running independent of the US server, and open to testing on eu.mining.eligius.st (but be aware, it's possibly less stable than the US server right now). I am also considering whether it will be possible to combine/merge the two continents' pools, so they assist each other rather than compete (as they do currently). This might require delaying payouts 1 block. I would appreciate everyone's opinion on whether a 1 block delay would be acceptable, and whether combining the pools is even something desirable.

Be sure you have PySide and ImageMagick installed first.

IMO, this can be a security risk. What if they don't arrive safely? Then someone has legitimate "counterfeit" Bitbills with no work at all...

The fees for the 1 BTC card seem a bit high... $3 fee+shipping for a $7 card?

See this post. Basically, that address owes the pool due to a bug. Is it you?

He didn't say he wanted more than one node running at a time.

Where is your miner located? Europe, by any chance? Also, check your system clock. It needs to be within 5 minutes of the correct time.

I run Lightfoot Hosting, and have my personal webpage on one of my VPS. Currently, Eligius (and BitGit) run on that same VPS.

I deployed an update tonight to finally solve (correctly) the malfunction last week where the pool neglected to pay miners... but apparently didn't test it well enough before making it live. When caching was enabled, it slowed down the merkle chain step by almost a minute, causing some intermittent connectivity issues. I noticed MySQL was bottlenecking, so began by trying to investigate how to optimize that, assuming it was growing pains (we reached over 50 GH/s today for the first time). What was really happening is that with the caching enabled, it was dividing the next block among all shares ever, rather than just since the last block. And once again, we had the worst timing possible to find the next block: it got distributed that way before I realized the full extent of the problem. This means the pool paid a total of 13 BTC to the wrong addresses. Since these 13 BTC actually went to other people, I can't just sendmany and correct like last time (other than out of my own pocket). I am therefore asking each of you who received excess payment to either continue (or begin) mining on the pool at least until the overpayment is paid off, or to make other arrangements with me to send the overpayment to the correct owners. Thanks, and apologizes to all who were underpaid-- I will make sure you get reimbursed eventually, even if I end up having to take it out of my own wallet.