moomoocow
Newbie
 Offline
Activity: 18
Merit: 0
|
 |
June 29, 2011, 10:37:03 PM |
|
This new system gives me a warm fuzzy feeling w.r.t. invalid blocks. They effectively don't matter as the slope continues to grow happily until a block is found =)
|
|
|
|
|
|
|
|
|
|
|
|
In order to achieve higher forum ranks, you need both activity points and merit points.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
Yeti
Member
Offline
Activity: 112
Merit: 10
Firstbits: 1yetiax
|
|
June 30, 2011, 07:09:14 AM |
|
Yup, you're right! When all the short rounds happened, I though "are we ever gonna need that much reserve?" But now that this round is taking forever plus the invalidated block last night I rest assured that I still get paid a more or less constant rate. I love it!
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?
|
|
|
|
|
Man From The Future
|
|
June 30, 2011, 12:59:53 PM |
|
Scratch that - it seems Phoernix miner fails with EU/s3, but not US, yet DiabloMiner works on S3, so I swapped  |
|
|
|
3phase
Sr. Member
Offline
Activity: 313
Merit: 251
Third score
|
|
June 30, 2011, 01:11:04 PM |
|
Scratch that - it seems Phoernix miner fails with EU/s3, but not US, yet DiabloMiner works on S3, so I swapped I have no problem with Phoenix on Eligius, in fact I get better results with it instead of poclbm (more accepted shares per hour). Connecting from Europe. |
|
|
|
|
Man From The Future
|
|
June 30, 2011, 01:20:49 PM |
|
From the UK. If I use poclbm, or phoenix, they regularly have networking issues, so I lose mining time. Phoenix 1.5, poclbm, whatever the newest one is  |
|
|
|
|
anodyne
|
|
June 30, 2011, 04:15:59 PM |
|
Seems we had an invalid block just recently. So, since the stats now show rounds rather than blocks I guess it makes sense to remove the invalid blocks from the table as the shares still are counted in the ongoing round – but, how about adding something in the table that indicates that a round includes invalid blocks?
|
Bitcoins: solid enough to build pyramids. |
|
|
Yeti
Member
Offline
Activity: 112
Merit: 10
Firstbits: 1yetiax
|
|
June 30, 2011, 04:39:46 PM |
|
I kinda like the "invalid" block stats because hiding them makes no sense. It's one thing to have a long round of 14+ hours and another thing if actually every round lasted roughly 5 hours but there were 3 invalid blocks. I'd like to know that!
|
|
|
|
shamathana
Newbie
Offline
Activity: 46
Merit: 0
|
|
June 30, 2011, 04:57:11 PM |
|
|
|
|
|
|
|
twmz
|
|
June 30, 2011, 04:58:53 PM |
|
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.
|
Was I helpful? 1 TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs WoT, GPGBitrated user: ewal. |
|
|
|
Carnth
|
|
June 30, 2011, 05: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. |
|
|
|
|
|
Carnth
|
|
June 30, 2011, 05: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. |
|
|
|
|
|
anodyne
|
|
June 30, 2011, 05: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.
|
Bitcoins: solid enough to build pyramids. |
|
|
Katapult
Newbie
Offline
Activity: 14
Merit: 0
|
|
June 30, 2011, 06: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-VnLrYI hope you enjoy! |
|
|
|
|
|
anodyne
|
|
June 30, 2011, 11: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. |
Bitcoins: solid enough to build pyramids. |
|
|
|
|
|
lebuen
|
|
July 01, 2011, 04:14:23 PM |
|
Still waiting for my unpaid rewards from EU - any updates?
|
|
|
|
|
mg101
Newbie
Offline
Activity: 23
Merit: 0
|
|
July 02, 2011, 01:25:09 AM |
|
Still waiting for my unpaid rewards from EU - any updates?
Same here...? |
|
|
|
|
|
anodyne
|
|
July 02, 2011, 01:42:02 AM |
|
Hmm. Both pool and website down? At least it looks that way both from my end and from isup.me
|
Bitcoins: solid enough to build pyramids. |
|
|
|
twmz
|
|
July 02, 2011, 03:05:32 AM |
|
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.
|
Was I helpful? 1 TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs WoT, GPGBitrated user: ewal. |
|
|
|
|
|
