Eligius works great for me. I connect to mining.eligius.st so that I automatically get redirected to the current pool, and I simultaneously run poclbm on my local bitcoind for solo mining.
That way, pool and solo mining get about 50% of the hashes each. But when Eligius is down, all of the hashes go to solo mining. Nothing is lost.
At my hash rate, a solo block is only going to come every year or so. But pooled mining will take a year or so to get 50 coins too, so that's OK.
Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 196. (Read 458480 times)
July 09, 2011, 09:17:42 AM
July 09, 2011, 09:04:32 AM
eligius is frustation. sorry but for now it looks like we will not return for quite some time. last payout was .4btc for several days of 1.3Gh/s. the interface was somewhat broken but as our monitoring showed the work was up and running, we didn't care much about eligius' reporting tools being offline. much trust to earn at this side 
i liked the concept.
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. i liked the concept.
July 09, 2011, 01:47:54 AM
Yeah I've been through 3 server migrations so far and it sucks lol, I guess experimental and stability don't go together but it looks like progress is being made.
July 09, 2011, 12:18:12 AM
I assume that balances from 3 or Ti are yet to be paid? Just checking. I got both my US and EU balances, so I have faith. If they have been sent, I guess I need to take a second look at my received. Thank you!
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. July 09, 2011, 12:07:47 AM
I assume that balances from 3 or Ti are yet to be paid? Just checking. I got both my US and EU balances, so I have faith. If they have been sent, I guess I need to take a second look at my received. Thank you!
July 08, 2011, 11:40:46 PM
[Recalled] - found stats page, etc.
July 08, 2011, 10:34:27 PM
Same here, it's the stability that concerns me the most. Hopefully this new server will be happy for the days to come.
July 08, 2011, 09:54:31 PM
I still having faith and love for this pool, however, i'm frustrated about its inestability, which workers hate.
July 08, 2011, 11:50:07 AM
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 pleasecall me (whois eligi.us) IM me (luke ... dashjr.org) if any of the following occur:
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.
There has been some trouble with the new bitcoind, so please
- 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.
July 08, 2011, 04:45:53 AM
You sir are a gentlemen and a scholar. I managed to use your instructions and I can now mine any pool over any port I feel like behind a rather restrictive firewall.
Glad that I could help. Some people might use this to mine behind firewalls or, at their own peril, on business machines. As Luke stated, port 80 works as well. I still have the intermittent problems if I try port 80 so I'm sticking to my solution for the time being.
I really want to see this pool succeed. I somewhat dislike proportional pools because they are quite easy for pool-hoppers to take advantage of. I showed a few friends 'the light' this evening and they are moving their 2GH/s rigs over from btcguild for a few days to see how it pans out. Hopefully they will stick around. The more power, the better!
July 07, 2011, 09:40:41 PM
Is the site shutdown?
July 07, 2011, 07:47:11 PM
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!
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!
July 07, 2011, 12:11:47 PM
You sir are a gentlemen and a scholar. I managed to use your instructions and I can now mine any pool over any port I feel like behind a rather restrictive firewall.
Do note that port 80 works on Eligius 
Got to give credit where credit is due! No more long-pool errors while connected to eligius over port 80! Thanks Luuke Jr!!
July 07, 2011, 10:29:46 AM
You sir are a gentlemen and a scholar. I managed to use your instructions and I can now mine any pool over any port I feel like behind a rather restrictive firewall.
Do note that port 80 works on Eligius July 07, 2011, 10:06:27 AM
btw,
if anyone else is experiencing network wonkiness trying to connect to eligius, you might want to consider a proxy. if you have servers at one site that are connecting reliably and another site that is failing to connect to mining.eligius.st even though ping works, you can try setting up an ssh tunnel to eligius through your working hosts. this has helped a few individuals and I have no idea what is going on from a network perspective on the server end.
if you do not have a remote host that is working, and you are experiencing connectivity issues and you are sure that the pool is up (according to the website), you can try doing what I did...
Install Tor, get it running, say, on the default port 9050... then fire off socat like this in another terminal:
socat TCP4-LISTEN:8399,fork SOCKS4A:localhost:mining.eligius.st:8337,socksport=9050
once socat is up (there will not be output to the console), simply direct your miners to localhost:8399 and you should get in without problems. I have been running like this for several hours now and have seen zero negative impact to hashrate or invalid counts. This has completely eliminated my issue of idle miners.
if anyone else is experiencing network wonkiness trying to connect to eligius, you might want to consider a proxy. if you have servers at one site that are connecting reliably and another site that is failing to connect to mining.eligius.st even though ping works, you can try setting up an ssh tunnel to eligius through your working hosts. this has helped a few individuals and I have no idea what is going on from a network perspective on the server end.
if you do not have a remote host that is working, and you are experiencing connectivity issues and you are sure that the pool is up (according to the website), you can try doing what I did...
Install Tor, get it running, say, on the default port 9050... then fire off socat like this in another terminal:
socat TCP4-LISTEN:8399,fork SOCKS4A:localhost:mining.eligius.st:8337,socksport=9050
once socat is up (there will not be output to the console), simply direct your miners to localhost:8399 and you should get in without problems. I have been running like this for several hours now and have seen zero negative impact to hashrate or invalid counts. This has completely eliminated my issue of idle miners.
You sir are a gentlemen and a scholar. I managed to use your instructions and I can now mine any pool over any port I feel like behind a rather restrictive firewall.
July 07, 2011, 06:50:31 AM
Depends on the transactions that are to be included in the block. These are transaction fees that Bitcoin users pay, i.e. the pool receives them and pays them to miners.
July 06, 2011, 06:34:21 PM
Any idea why the pool has missed its chance to pay me on the last three blocks?
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.how much is the transaction fee?
July 06, 2011, 05:52:08 PM
Any idea why the pool has missed its chance to pay me on the last three blocks?
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. July 06, 2011, 04:57:24 PM
Any idea why the pool has missed its chance to pay me on the last three blocks?
July 06, 2011, 02:07:13 PM
I'm still waiting my unpaid EU balance. The US one was received promptly when Luke-Jr said it would, but nothing yet for EU.
it took quite a while, but mine are all through now.Jump to: