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.
http://forum.bitcoin.org/index.php?topic=25537.0 
Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 198. (Read 458518 times)
July 03, 2011, 07:44:26 AM
July 03, 2011, 07:37:57 AM
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.
July 02, 2011, 05:58:39 PM
You can't see individual stats for each worker unless you give each its own address (which might cause you to get spammed with small transactions once they come over the threshold), but otherwise I think Artefact2 has built one of the most detailed stats pages of any pool.
if you do that you need to copy paste one address for each worker and when you want to checks stats will be a pain 
July 02, 2011, 12:00:18 PM
It sounds like the EU payments are set up to be sent as transactions, like happened with the outstanding US balance.
July 02, 2011, 11:57:01 AM
Payout from the EU pool is visible now in my client (11 more blocks needed).
http://blockexplorer.com/b/134233
Now that I think about it, it's possible that the payout was from the s3 pool, I'm not really sure. http://blockexplorer.com/b/134233
July 02, 2011, 10:29:04 AM
Payout from the EU pool is visible now in my client (11 more blocks needed).
http://blockexplorer.com/b/134233
http://blockexplorer.com/b/134233
I didn't get any payout for my unpaid EU balance yet, and my address isn't showing up in that block.
If this block is indeed from EU, it seems that the pool was withholding more than 50BTC and is still withholding the remainder.
Edit: News:
Quote
[17:54] Am I right with the assumption, that after the the server is fixed and another block is found, the EU payouts will happen for real? (Yes, I know there's "Europe balances were paid off Friday morning." in the topic, but apparently this didn't happen.)
[17:54] <@luke-jr> ulee: in theory :|
[17:54] <@luke-jr> ulee: I might have to fire up the EU bitcoind again to rexmit it
[17:54] <@luke-jr> ulee: in theory :|
[17:54] <@luke-jr> ulee: I might have to fire up the EU bitcoind again to rexmit it
July 02, 2011, 10:13:52 AM
You get pretty nifty stats (when they are working). Here's a screenshot I had for the hashrate graph for two miners on the somewhat cranky EU pool:
You can't see individual stats for each worker unless you give each its own address (which might cause you to get spammed with small transactions once they come over the threshold), but otherwise I think Artefact2 has built one of the most detailed stats pages of any pool.
You can't see individual stats for each worker unless you give each its own address (which might cause you to get spammed with small transactions once they come over the threshold), but otherwise I think Artefact2 has built one of the most detailed stats pages of any pool.
July 02, 2011, 03:02:27 AM
Payout from the EU pool is visible now in my client (11 more blocks needed).
http://blockexplorer.com/b/134233
http://blockexplorer.com/b/134233
July 01, 2011, 10:05:32 PM
EU payout transaction was sent, but it likely won't appear in a block until Eligius finds a block.
The pool server is down currently. I don't know what the ETA is for it it being resolved.
Note, because the pool is down, the EU payout transaction is in limbo as Eligius can't find blocks. So it will not get confirmed until the pool server is fixed and a block is found.
The pool server is down currently. I don't know what the ETA is for it it being resolved.
Note, because the pool is down, the EU payout transaction is in limbo as Eligius can't find blocks. So it will not get confirmed until the pool server is fixed and a block is found.
July 01, 2011, 08:42:02 PM
Hmm. Both pool and website down? At least it looks that way both from my end and from isup.me
July 01, 2011, 08:25:09 PM
Still waiting for my unpaid rewards from EU - any updates?
Same here...?
July 01, 2011, 11:14:23 AM
Still waiting for my unpaid rewards from EU - any updates?
July 01, 2011, 02:17:32 AM
http://forum.bitcoin.org/index.php?topic=24448.0 - do you know about this?
are you servers protected against botnet account/mining?
June 30, 2011, 06:46:22 PM
By the way, how do you handle payouts of more than 50 BTC? I can imagine on the next block people will have stored up so much reward that it cannot fit in the "generate" part. Will there also be transfers for some people or will payouts be shifted to another block in a short round?
In the recent short blocks the pool seems to be keeping only 1 satoshi instead of the value of remaining shares – I'm guessing it's set up to order the repayment of credits from small to large, so by paying the small amounts first it limits the number of payments that don't fit in generation and have to be sent by transaction.
June 30, 2011, 01:42:40 PM
For anyone considering starting up mining, I created a walkthrough video on youtube on how to install the bitcoin wallet, how to install a miner, configure it, and start mining on Eligius. http://www.youtube.com/watch?v=3L9zO-VnLrY
I hope you enjoy!
I hope you enjoy!
June 30, 2011, 12:58:24 PM
Maybe the simplest way would be to mark the lines for the invalid block and the following round with the same color and add something like "included in ongoing round" in the last column to explain that the stats listed for the invalid block are carried over and still count.
June 30, 2011, 12:07:19 PM
{Edit-Removed double negatives} It's also true that invalid blocks matter, right? Too many invalid blocks will push our "long round vs short round" ratio more towards long rounds. SMPPS works well when long and short rounds are balanced over time. More long rounds artificially caused by invalid blocks will "break" that underlying assumption.
This is absolutely correct. If an invalid block occurs... it's as if the block didn't occur at all (according to the pool) and makes the rounds longer.I don't like that invalid block are hidden because it makes it harder to notice if there is a problem.
I agree again. We should have all blocks solved...valid or invalid listed in the stats. Please don't change it.The more info we (the pool members) have the better.
June 30, 2011, 12:00:40 PM
By the way, how do you handle payouts of more than 50 BTC? I can imagine on the next block people will have stored up so much reward that it cannot fit in the "generate" part.
The pool will never payout more than 50BTC per block generated.
Quick Explanation:
If the current block takes so long that Pay Per Share has "used up all 50BTC." then the pool will revert to proportional payout.
Long Explanation:
The pool is on a Max Pay Per Share payout system.
This means that the if a new block is solved faster than normal... and the Pay Per Share payout to everyone was only 40BTC... the pool will save the left over 10BTC for later.
Then if a particularly long block happens.. and the Pay Per Share payout happens to be 60 BTC. The pool will use the saved 10BTC from the previous block to help pay for the shares.
THEN... if another long block occurs, and the Pay Per Share is 60BTC (again). The pool will pay out only 50BTC on a proportional basis.
If there are several short blocks in a row (like we just had), then the pool will save all of the extra BTC for later.
You will never be able to get all of that stored BTC until your miners submit as many shares as it takes to earn back all of the stored BTC.
So, to sum up:
Short blocks will help pay for long blocks--this will help keep everything more averaged.
June 30, 2011, 11:58:53 AM
It's also not true that invalid blocks don't matter, right? Too many invalid blocks will push our "long round vs short round" ratio more towards long rounds. SMPPS works well when long and short rounds are balanced over time. More long rounds artificially caused by invalid blocks will "break" that underlying assumption.
I don't like that invalid block are hidden because it makes it harder to notice if there is a problem. We shouldn't have statistically more invalid blocks than other pools, but it seems like we do.
I don't like that invalid block are hidden because it makes it harder to notice if there is a problem. We shouldn't have statistically more invalid blocks than other pools, but it seems like we do.
June 30, 2011, 11:57:11 AM
that's happening quite often.
Jump to: