It's normal for the pool to be wrong about your hash rate, because it's trying to guess the hash rate based on how many proofs of work you send in, which again depends on luck. But... a deviation that large over 10 rounds, that sounds like something is very wrong.


That's pretty high. Perhaps you are having issues with long polling. On my pool I had to make all sorts of adjustments to make this work well. If you have a home router that times out connections after just a few minutes you may want to change that timeout if possible.

Also, if your internet connection is unstable (comes and goes) that can cause your miner to resubmit the same proofs of work multiple times, which will cause some rejects.

Do you have any error messages from the miner?


That depends on how much you pay for electricity and what else you have in the computer that uses electricity while it's on.

Happy birthday, BitMinter. Today it is 1 year since the pool opened for users, and we are minting coins like never before 

Today it is 1 year since BitMinter opened.

And look at the luck we're having today. We're celebrating with coins instead of cake!

PS: It's ok to also have some cake.

Thanks that would be great. Yep, I have TeamViewer. Use PM or operator@bitminter.com for details.

Wow, Skynet in the making

With a good miner program and pool you should easily stay below 1% stale.

Maybe easyminer is not actually measuring the hash rate? Is it not deviating from 864 mh/s at all?

When I added BFL support to my miner I even made it drop hash rate on block changes according to how many hashes are wasted. The way BFL devices work you waste some hashes on every block change when you cancel the old work. That's because the device has already done some work but there is no way to get the results (if any) when you cancel. At that point the work result is stale anyway, you'd want to get the results as they are found so you can make use of them.

So what to display? The work being done? Or the work that is actually useful, the effective hash rate? I decided to go with the latter. Not sure what cgminer is doing.

Try BitMinter client (bitminter.com). Works fine on Mac OS X with GPU or BFL FPGA devices. Support for Icarus and Cairnsmore FPGAs coming soon.

Try BitMinter client. You can set a schedule for when to mine and you can minimize it to the systray. bitminter.com

For the next miner version I'd like to add support for Icarus and Cairnsmore FPGA devices. If you can give me remote access to a computer with one for testing, please let me know.

rollntime will do just fine. If you don't want to roll even 1 second into the future and you need 3 nonce ranges per second, just get 3 sets of rollable work data. Problem solved. Also, being a few seconds into the future (or the past) is ok.

The other option besides rollntime is generating work locally and using getmemorypool (BIP22 as Pieter Wuille already mentioned) instead of getwork.

There's no need to change the format of bitcoin blocks.

Anyone have a machine with an Icarus or Cairnsmore that they can give me remote access to?

Working on support for those devices in the BitMinter client and need a test system.

That already exists. It's called rollntime. Sadly miner support isn't very good. To make good use of rollntime the miner should 1: make the best use of the roll range it is given, and 2: never roll further than the server allows ("expire" support).

In my pool I whitelist miners with proper rollntime support. Others don't get rollable work. Currently only DiabloMiner and my own miner (although I'm only now working on actual support in the miner). I will have a look at MPBM and possibly add that. I hope other miners will improve support and I'll whitelist them as they come out. I think ASIC mining without this could be a very bad idea.


If someone gets (through rollntime) 100 work units (nonce ranges) from my pool in 1 request and then send in 100 proofs of work then processing the proofs of work is what's causing server load. Many seem to believe that processing proofs of work is free, but I think we'll see this proven wrong in october. 


Yeah. The bitcoin world is in constant change, and it's always do or die for developers.

Miner support for >1 difficulty isn't looking so good: https://en.bitcoin.it/wiki/Getwork_support

But maybe it just needs updating?

Glad you like it - welcome to the minting team


Indeed it seems to work great. Congrats on that BTC block. 

It's because I restarted the mining backend. After that it takes a few minutes before it has hash rates to display.

There were some problems with dead sockets on the server. Networking on the server is looking so much better with this fixed.

Strange thing. The backend was bound on ipv6 and Linux was automatically mapping incoming ipv4 connections over to ipv6. Apparently this is what left piles of dead sockets. After making sure it binds to ipv4 there is no mapping and everything is fine.

The BFL ASIC discussion:
https://bitcointalk.org/index.php?topic=87934.0

Btw, sorry for connection problems to website and port 80 mining right now. The site is getting much busier and I had to increase some server limits. Should be OK again now.

Lazy sunday update. Fixed URLs for auto cash outs in transaction history that were not working. Also switched blockexplorer URLs over to blockchain.info. I think it's an easier to understand and better looking site.

We are now 9 days away from 1 year of public operation (since 26.06.2011) !

If anyone is having problems running the BitMinter client after upgrading to the latest Java, try clearing Java's temporary internet files and starting it again. You find Java temporary internet files in the Java control panel. If using Windows you will find the Java control panel under the Windows control panel. On any OS you can also get to it with "javaws -viewer" on the command line.

DDoS is difficult to prevent, especially for a mining pool that looks like a DDoS when operating normally. But I'll look into what can be done.

By the way, if anyone is having problems running the BitMinter client after upgrading to the latest Java, try clearing Java's temporary internet files and starting it again. You find Java temporary internet files in the Java control panel. If using Windows it will be in the Windows control panel. On any OS you can get it with "javaws -viewer" on the command line.