I have 2 miners actively running from 2 different geographic locations just to make sure that our server is reachable.  At this point in time, both of them are able to pull a getwork, solve it, then send it back.  Can you ping bitcoinpool.com??  Can you reach the website?

FML.  You're correct.  We have been tracking the wrong block.  We forgot to add 1 to the block number when it's found.  Current blocks in the network != the current block being worked on.
SHIT SHIT SHIT

Will fix this weekend.

OK slush, enjoy this.  I'M SORRY

See, your site does have a bug in it's stats page.  This has nothing to do with bitcoind.  I don't have this problem, Tycho doesn't either.  Maybe it's cause you use more than one bitcoind, who knows??  Apparently you don't know either.

Please note the above picture is from slush's site, not ours.
Had to be clear about that.

And Slush says we're the ones that are wrong?!  Really?  Our site doesn't do the same types double listing his does.
So who's site is wrong and buggy here?  Not ours and Not Tycho's (deepbit).

I'm looking into this now.  Should have an update soon.


See, slush's stats page has problem.  Look at block 115147.  It's listed two times.  The bottom link for 115147 takes you to that block in block explorer.  The link right above it for the same block, 115147, takes you to blockexplorer where you see an error "No such block".  Slush's stats are wrong sometimes and have bugs in it. 
Ours is correct.  Check every link on our blocks page if you want, they're all correct.

No Slush, you are wrong.  See my picture, where's yours if you really got it? 
It's important to track this correctly, and you've openly admitted (and it's still visible) that your site seems to have a problem tracking blocks.

Our site tracks blocks just fine with no problems.  Why don't you fix your own site before you try and criticize other people's pool.  Tycho and us don't seem to have the same problems you do.

We're still crunching away with 96 active users.  You might want to double check your setup.

Yes, I'm sure because I got paid for it!  



Check yourself.
Block 114974: http://bitcoinpool.com/block.php?block=114974
Block 114952: http://bitcoinpool.com/block.php?block=114952

If you look at our stats page for the block, you'll see that the payouts match that of "goldy1" (my miners). Note that block 114952 it says I got paid "1.17805453", which if you round up is 1.18, which makes what's in my wallet.

I guess this is that bug in slush's pool he's talked about.  I was on the fence about what truthHurts was saying, but now I'm leaning towards the side that he was probably correct, and it was a bug that exposed what slush is doing to his users. I'm not going to get into that though...that appears to be an entirely separate thread on it's own.

THIS IS WHY WE HAVE FULL STATS OF EACH BLOCK AND WHO GOT PAID HOW MUCH, SO WHEN THIS HAPPENS YOU KNOW WHO'S LYING AND WHO IS NOT!

I've been looking into it today for just a minute. It seems like a far more efficient way to pay miners.
Where is the patch for bitcoind at, or is it in the latest github of bitcoin?

Thanks for looking out.  I hope this crap with the network ends soon.

What miner are you using?
Are you sure you used the correct login/pass?

Please read thread: 

http://bitcointalk.org/index.php?topic=4291.msg72561#msg72561

Short of it: the entire bitcoin network is being flooded.  Nothing we can do.  Everybody is experiencing this.  Sorry.

Positive Feedback: The text color is so light that it's hard to read on some monitors.  A slight bit darker would be easier on the eyes.
Other than that, looks good!

Here is the quick fix if you're using windows:

Create a new batch script.  I call mine  "Start Mining.bat"
It should contain the following code.


That will automatically restart poclbm-mod if it crashes.  Hope that helps you until we track down the problem.

We have heard about this from 1 other user.  It's kinda hit and miss when trying to debug this since the output log from the other user contained no debug information and no errors or execeptions.  Between Geebus and I, we test our miner on Windows 7 32bit and 64bit, Windows XP 32bit, and Ubuntu server 10.04.  If it works for a round on these systems, we then release it publicly.

We sure could use your help to diagnose this problem.  Please include the following information.

• What OS you're using.
• 32 or 64 bit?
• The make and model of your video card.
• How many video cards you are using.
• The make and model of your motherboard.
• The make and model of your CPU.
• The speed of your CPU, the speed of your FSB, and the speed of your memory.
• Please use the "--log" option to get an output log.  This will tell us about what time it crashed, and how long it ran before it crashed.
• Driver version (Catalyst version, or GeForce version)
• AMDAPP SDK or nVidia OpenCL SDK version

Sorry it's not working as expected.  I hope we can track down the bug and get it fixed soon.  We like it when our miners can work 24/7 without a problem.

Thank you for the feedback.

EDIT: Added Geebus's recommendations to this post.

PATIENCE PLEASE

1) From the time I go to sleep to the time I wake up, there are generally a couple dozen posts.  I'm more worried about my day job from the time I wake up to the time I get home, so if I don't reply to your post within an hour or six after you post it, please try and keep in mind that running this pool doesn't count as my day job and I'm doing my best to juggle my personal life, work life, and bitcoin life.

2) When over half the new posts on this thread are just flames from the trolls who quotes the entire message from another user, it immediately kicks in my mental BullShit/Troll filter as I try to ignore them.  Sometime's I will miss a valid question or concern because it has 4 posts before and 5 posts after it from the troll.  So if I missed your question, I apologize in advance.  If you're feeling ignored, don't be afraid to PM me.

3) We know that someone is flooding the bitcoin network with transactions.  You will get paid as soon as the network can work through all the transactions.


Thank you for your patience.

bobR, it's rude and confusing to others not get our names correct.
It is "Geebus" and "Fairuser".
Please double check you spelling, punctuation, and grammer before you hit the "post" button.
Thank you.

Yes.  It appears someone is flooding the bitcoin network with hundreds of mini payments, and it's causing this very long delay in anyone getting paid.  Why they're doing this, I don't know.  They don't gain anything from it other than being an asshole and causing everyone to wait.

Patience is required at this point. 
I got about 7.84 btc waiting to be confirmed.

You are correct.  By default we set it to 0.01 when you signup.  Some people have requested the ability to change this, and now you can.

We have hit ~10 Ghash/s and we found 3 blocks today!  WOOT! 

Here's some stats about how well the server is handling all this work. 

• The server is running directly on hardware dedicated to this pool.  It is not running on a VPS on a over loaded server like some other pools.
• At about 10 Ghash/s, it's only using ~ 14KBytes/s of bandwidth. We can handle 51,200KB/s, or ~3,600 Ghash/s at this ratio.
• CPU usage is anywhere between 100-200% (Quad-core can handle 400% at max capacity).
• Memory is using about 6.5GB out of 12GB.
• We have a 1TB drive, and it's nowhere close to being full.

All and all, I would say that the server is doing very well and can handle more traffic, so tell your friends about us.  We're ready to take all the traffic and users we can get.  Remember, we're the only pool not charging fees, we're running on dedicated hardware, and have a direct fiber connection to the internet which gives us an extremely low latency and high bandwidth.

I would like to say THANK YOU to all the miners on our pool that are using our modified miner.  Because of you, the load and resources used are substantially lower than what they would be if you used a different miner.  Thank you, thank you very much.

I thought about that, but it doesn't look like the nonce start at 0x00000000 and working sequentially towards 0xFFFFFFFF based on the results from miner logs.  If it was sequential then this would be a lot easier to figure out server side.  I haven't looking at the BitcoinMiner.cl in depth, so I do not know how it is picking it's nonces.  I guess if we could predict how the BitcoinMiner.cl kernel generates nonces, then maybe we could figure out the percentage of getwork the nonce was found at.

I suspect further investigating will tell.