best mining pool for developers?

[eldentyrell_old]

Hi, I'm developing some experimental mining hardware.

I was wondering if any of the pools have particularly good statistics/feedback on things like stale blocks, invalid blocks, etc.  Even better would be showing you a list of your submitted shares and what the pool thought of each of them.

I've been using eligius.st but they don't update their statistics very often and don't tell you why they rejected a block (i.e. stale vs. bad hash, etc).  I software-check my shares before submitting, but something just doesn't add up.

At this point I don't care about payout ratios/schemes; running at debug speeds the earnings are negligible.

Thanks!

[1714778655]

1714778655

[1714778655]

1714778655

[1714778655]

1714778655

[eldentyrell_old]

I should add that I don't support long-poll yet, and there's other stuff I need to fix first, so knowing the difference between stale shares and bad shares is important.

[eldentyrell_old]

Okay, this is totally messed up.  I've sent eligius.st FIVE shares now and it's claiming that ALL of them are stale.  Each was submitted no more than 400 seconds after the getwork.

Something is wrong here.

Either my shares are bad (bug in my code) and eligius.st doesn't know the difference between "invalid" and "stale", or else eligius.st has a bug.

[eldentyrell_old]

Total so far:

Stale shares: 11

Valid shares: 0

Something is wrong with eligius.  Either it's reporting "wrong" shares as "stale", or else it's just broken.

I'm going to try other pools.

[eldentyrell_old]

Figured it out, I was neglecting to fill in the "data" field.

[tristian1980]

Did you try deepbit?

[Luke-Jr]

I've been using eligius.st but they don't update their statistics very often and don't tell you why they rejected a block (i.e. stale vs. bad hash, etc).

Um, what? Direct access to the PostgreSQL database is available, and every submission returns the rejection reason in the headers...

[Meni Rosenfeld]

I've been using eligius.st but they don't update their statistics very often and don't tell you why they rejected a block (i.e. stale vs. bad hash, etc).

Um, what? Direct access to the PostgreSQL database is available, and every submission returns the rejection reason in the headers...

Maybe this wasn't the case 1 year ago when this thread was started, before tristian1980 went on a necro spree.