Author

Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 197. (Read 458255 times)

newbie
Activity: 42
Merit: 0
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?
legendary
Activity: 2576
Merit: 1186
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.
newbie
Activity: 42
Merit: 0
Any idea why the pool has missed its chance to pay me on the last three blocks?

newbie
Activity: 8
Merit: 0
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.
I received mine EU balance yesterday. Just wait for the next block...
sr. member
Activity: 371
Merit: 250
I had one miner failing to connect intermittently and realized that one was connected to mining.eligius.st, while the other machine has been pointed to s3.mining.etc... since the change from EU server. So, I pointed the first one to that address as well, and I haven't noticed any connection problems since then.

If it has anything to do with the local connections or the redirection on the server end is beyond me, though.

All now appear to point to teh same IP, ending in .78.7, although a while ago one pointed to .78.8. :S

luke-jr, which is the correct server? Tongue
full member
Activity: 518
Merit: 100
I had one miner failing to connect intermittently and realized that one was connected to mining.eligius.st, while the other machine has been pointed to s3.mining.etc... since the change from EU server. So, I pointed the first one to that address as well, and I haven't noticed any connection problems since then.

If it has anything to do with the local connections or the redirection on the server end is beyond me, though.
newbie
Activity: 11
Merit: 0
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.

newbie
Activity: 46
Merit: 0
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.
full member
Activity: 518
Merit: 100
So maybe "maximum reward" is the amount of BTC we will be awarded in the future, if the pool has a few lucky rounds?
Yes

Isn't it the opposite... the pool had lucky rounds before, and the maximum reward is the amount you get back from the overhead if the current round ends right now?

Edit: I got that backwards. I blame it on just having gotten out of bed with a fever...  Tongue


Anyway, even though the pool stats won't admit it yet, it seems that a block was produced, and that outstanding EU payments are included: http://blockexplorer.com/b/134863 (4 confirmations atm)
legendary
Activity: 2576
Merit: 1186
It seems like Eligius will NOT find a block, unless something gets corrected. I am mining at Slush also, I get the new block notifications there, but no such notifications on Eligius.
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).
sr. member
Activity: 313
Merit: 251
Third score

How long of a round are you currently going on? I don't have miners at Eligius atm.

I just didn't see any "LP: New work pushed" with Phoenix on Eligius for an hour or so (hundreds of shares accepted in the meantime). I thought WTF?

So I switched a miner to Slush pool, watched the new block messages appearing there, but no such messages on my Eligius miners. I let it run for an hour again to be sure.

Switched them all from Eligius, no use mining if no blocks can be  found.



sr. member
Activity: 252
Merit: 251

It seems like Eligius will NOT find a block, unless something gets corrected. I am mining at Slush also, I get the new block notifications there, but no such notifications on Eligius.

How long of a round are you currently going on? I don't have miners at Eligius atm.
sr. member
Activity: 313
Merit: 251
Third score

It seems like Eligius will NOT find a block, unless something gets corrected. I am mining at Slush also, I get the new block notifications there, but no such notifications on Eligius.
legendary
Activity: 2576
Merit: 1186
so I guess "block estimate" is wavering up and down because my share of the pool is changing, which normally doesn't matter under PPS but does matter now that the total payout has exceeded 50 BTC?
Specifically, the total payout-if-this-were-PPS exceeded 50+64 (excess from past blocks) = 114 BTC.
hero member
Activity: 737
Merit: 500
So maybe "maximum reward" is the amount of BTC we will be awarded in the future, if the pool has a few lucky rounds?

Yes
newbie
Activity: 42
Merit: 0
As my "block estimate" currently goes down, I assume the pool has used up all its savings. At the same time, "Maximum reward" goes up like I expect my reward to do in a pure PPS scenario.

So maybe "maximum reward" is the amount of BTC we will be awarded in the future, if the pool has a few lucky rounds?
That would make sense... so I guess "block estimate" is wavering up and down because my share of the pool is changing, which normally doesn't matter under PPS but does matter now that the total payout has exceeded 50 BTC?
member
Activity: 98
Merit: 10
What exactly do "current block estimate" and "maximum reward" mean in Artefact2's stats?

I'm wondering the same. As my "block estimate" currently goes down, I assume the pool has used up all its savings. At the same time, "Maximum reward" goes up like I expect my reward to do in a pure PPS scenario.

So maybe "maximum reward" is the amount of BTC we will be awarded in the future, if the pool has a few lucky rounds?
newbie
Activity: 42
Merit: 0
What exactly do "current block estimate" and "maximum reward" mean in Artefact2's stats?
member
Activity: 98
Merit: 10
Luke-Jr posted that the transaction is currently being broadcasted to the bitcoin network, however there appear to be no pools (besides eligius itself) that accept this transaction.

So the transaction will probably be processed when the eligius pool finds a block.
hero member
Activity: 608
Merit: 500
Hey guys, I appear to have been paid for my US server shares on Eligius but the EU server hasn't yet paid me out-I thought these went out on Thursday?
User was 1MmQrK8uv8AitWUNSMmK3HPeq3BjE31efa
Jump to: