[1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration!

[PoulGrym]

I think the pool's been down for 3h or more.. What's going on? At least I've got a backup set. Still that's not much better.

[1714144067]

1714144067

[MrWizard]

Pool is down until Inaba wakes up and restarts the server.

[Inaba]

Yeah those changes that I made seem to have introduced a problem.  I'm looking into it now, it's back up.

[WebMonkey]

i wasn't "down" long but have been disappointed with my estimated earnings for this round.

since the "big boys" have come to play, my est. is .199 for almost 3 days work.  should be closer to .5

i run only 200mH 24/7 and an XTRA 360mH about 14 hours a day.

i know, things even out but they used to be a little more even.

=]

i hope i don't sound TOO whiney.  just leaving some comments from one of the "little people" in the pool.

still, only pool i swim in these days.

'monkey

[village.idiot]

Yeah, I've been noticing the same thing.  When I finally got my miners running there were only about 120 miners in the pool and I used to make .25BTC or so working part time but since then I have seen twice as many miners and I'm only getting the BTC dust off the floor.

I don't know how all the numbers work out but I seem to do better in a small pool.  This cold just be my misunderstanding of everything.

Not complaining, Inaba

[WebMonkey]

just a long, unlucky block.

the "mental" problem for me is:  can i make up the diff on a short block with all the "big boys" generating a higher "score" than i.

=]

great pool though inaba, best feature set ever.  just one o dem tings...

'monkey

[supersonic3974]

Did the difficulty go up between the last block and this one?

[Inaba]

Nope, same as before.  We're paying for that lucky streak it seems.  Screw you probability!

[Inaba]

Ok, scoring is in place for this round. When it solves it will be awarded based on scoring not proportional.

I've tested all the code I possibly can locally without an actual solved block (I tested it against the previous block) - but something always seems to crop up unexpectedly. Hopefully that's not the case and the scoring should go off without a hitch.

I will post the details of the round once the block solves. Assuming everything is good, I will then automate the system to provide those details for each block.

I could provide individual shares as downloadable content, but the effort involved in that is pretty substantial and disk space is fairly large, especially for rounds as large as this (gzipped round data for block 18 and 19 weighs in at 490 MB so far) and I'd rather not keep that data around if nobody wants it. Developing a distribution system for that will take away time from adding other, in my opinion, more important features, but if enough people feel the need for that data, I will provide it in the interests of transparency and auditing.

As a side note, for the moment your "Estimated Rewards" is still based off of proportional. This is accurate assuming you aren't pool hopping - however, I will look into getting a different method of estimation, but with a scoring system, any estimation is really meaningless anyway since we don't know when the round will end.

[WebMonkey]

i say work on what you need to Inaba.  that data isn't crucial to my stay in the pool.
=]

'monkey

[btcboston]

As a side note, for the moment your "Estimated Rewards" is still based off of proportional. This is accurate assuming you aren't pool hopping - however, I will look into getting a different method of estimation, but with a scoring system, any estimation is really meaningless anyway since we don't know when the round will end.

In a score based system I would say the estimated reward should be something like -- calculate based on if the round ended right now, and scores were determined, what the reward would be.  I'm not sure how much calculation is required for this...maybe it could be done every 10-15 minutes and refreshed on each user's account page? 

[Inaba]

Yeah that's probably the way I'll end up going.  I need to make some modifications to the getwork server to record the appropriate data in the database though and I'm still working through the bitcoind problem at the moment, I may have a fix for it but I don't want to put it in tonight before bed until I can keep an eye on it.

[sceptre]

@Inaba
I tried to register on your forum but I did not get my confirmation e-mail and I can't reset the password because your e-mails never arrive at my gmail account (not in SPAM).

I would like to report that I am getting a lot of rejected shares on your pool. On others I get around 0.6% but on yours it is way too high. 270Mh/s, 468 Accepted, 35 rejected (6.93%)
This is not the first test. My first attempt at mining at your pool ended with an idle phoenix, about 3000 submitted shares and also ~6% rejects.

Not sure what is going on but this is too much for me. I know it is not on my end because my miners will run "forever" on other pools.

[Inaba]

I don't see your user name in the database, so I can't tell you what's happening with your email.  I do know that plenty of people are receiving emails at gmail addresses with no problems.  The only major provider that has a problem is yahoo and it's subsidiaries (like rogers) - but that's an internetwide problem and not really a problem with the email.  Yahoo has always had trouble accepting email from random places (It boggles me that anyone still has a yahoo email address actually).

As far as the stales go - Are you on the US or EU server?  I had to switch the bitcoind daemon back to the slow one last night while I work out a freeze bug in the optimized version.  I should have the new one back in place this weekend and it should resolve the stale issues.  I am going to be making some other changes as well to help that out.

[Darioux]

Just wanna say that I have been mining with this pool for last several blocks but Im not sure if I'm gonna continue as can't undenstand (and do not trust) the new scoring system. It was a great pool before and love the website, but I rather to keep things simple and not planning on doing a maths degree to work out how the scores are calculated. Just wonder how many people here do actually understand it and more importantly how many people support it.

[village.idiot]

I don't know anything about the scoring system.  I just hope Inaba wouldn't do something that would hurt the little guy.
My two 5770s don't seem to be finding as much BTC as they used to before the big rigs moved in.
I'm still trying to get mine running right and get it mining 24/7

[Inaba]

I realize it seems to be confusing, but you don't really have to worry about the math.  There are two take aways to understand about the scoring system:

1. The scoring system is to protect you from pool hoppers taking a portion of your proceeds.
2. You won't see a difference in your income if you are not a pool hopper (Well, you may see a slight increase in your income).

A quick explanation of the scoring system in simplified terms:

Each share is worth a certain amount of points plus the value of the share submitted just before it. At the end of a round, all of the shares scores are added up to come up with a number.  All of your shares are added together and your number is divided by the score of all the shares and that is your reward.

Other than that, there's nothing else to really worry about in regards to the scoring system.  The only reason I post so much information is for transparency and so that people know everything is legitimate.  It's also good to have more than one set of eyes looking at it in case I were to miss something.

[Shevek]

Block #19 solved... or not? 

It appears in the list with no date, but with 8 confirmations (at the moment). Blockexplorer says it is ok.

eclipsemc.com shows frontpage as if the block was not solved... no expected reward

What happens!?

[Inaba]

Yeah the scoring script died - well, the script works fine but mysql bombed because there are over 6 million rows in the DB and I did not have the lock buffers set high enough to handle that so it was choking.  I upped them and the block is processing now but it's slow going.  I will be changing the way share counts are calculated going forward so it won't take so long to process a block. 

This block should be finished processing in another 30 minutes or so.  No information is being lost and your share counts are going towards the next block even if it appears they are going towards the last block   I know I keep saying it, but I want to be sure everyone is aware that all display stuff is complete separate from calculation information, this is to ensure that things like this don't affect you monetarily.  Everything is double checked and cross compared before being committed to the DB.

All is well and the monster block has been solved!

[WebMonkey]

thanks for the update Inaba.

and now, back to your regular scheduled programming.....

=]

'monkey