80 GH/s is about 0.018 BTC per day now, on average.

Rewards are a little below expected due to some bad luck a couple days back.

You can see the stats here: https://bitminter.com/stats/rewards

That's the last 500 shifts. About 1000 hours.

That's the problem. You can use _ or . to separate user and worker names. In this case it mines as user "bens" with worker "btc_ant11". Which doesn't exist. Go to "my account" -> "workers" in the website menu and create a new worker by filling out a name at the button of the table and clicking the plus symbol.


More than five workers is a perk. Most users have enough with five workers though.

I believe these appear as a USB HID device, rather than a COM (serial) port. So they are more work to add (only have OpenCL and COM ports so far). Would be nice, though, but no specific plans at the moment.

Maybe, if you like hashing at reduced speed and having it quit on you while you are asleep.

But this sort of humor is not recommended.

Currently only Butterfly Labs and ASICMiner Block Erupter USB sticks. I added support for Red Fury, but it's not working well for most people, so I suggest using bfgminer instead. The problems are proving hard to fix so far.

I plan to add support for Antminer U1 soon.

There's a short feature list in the Bitminter client thread: https://bitcointalk.org/index.php?topic=31163

Antminer support is not ready yet.

The client will detect it (wrongly) as an Icarus, because it appears to behave like one. It will run at reduced hashrate while spewing errors. After a while it will hit too many errors in a row and the client will give up on it.

This is not recommended.

Actual Antminer support coming soon I hope.

If it has locked up completely (crashed), then it will just show whatever was the situation before it failed. For most users it runs stable, but a few have reported that it uses more and more memory until it gets sluggish and eventually locks up. I'm looking into this. It might help if you can tell me which mining devices you are mining with. The users who experience this problem must have something in common.


As far as I could see we had no server issues yesterday.

Was your mining client's config changed to mine at another pool?

You can check your average hashrate in the shifts at https://bitminter.com/shifts - that might be useful to figure out what happened.

I hope to fix the hashrate issue. But the problem with it not detecting them as easily as bfgminer does, I have no idea what the problem is.

If you know how to use the command line, a simple way to run bfgminer:

Yep, that will work. Just don't run the same devices in both clients.

Not sure what you are doing wrong with bfgminer. If it only says that the pool is requesting work updates, but never "accepted", then something is wrong.

Edit: "accepted" lines you should get with every accepted proof of work (aka "share"), which is what you get paid for. You should see those lines output in bfgminer regularly while the ASIC is working.

There is some info about worker difficulty and the easy mode perk here: https://bitcointalk.org/index.php?topic=27062.msg3142713#msg3142713

Some blocks do get orphaned, but this is much less frequent than it used to be.

"Send coins" functionality added (aka manual cash out)

You can access it under the "my account" menu, or through the links on the account details page, in the current balance table.

This allows cashing out very small amounts. We can't pay the fee for these like we do for auto cash out, though. Mind the warning about collecting many tiny payments in your wallet. Doing so will cause higher fees for you in the future when you send those coins elsewhere.

Some have issues getting it detected by Bitminter client, and some have problems with reduced hashrate. Hopefully I will be able to fix this in the future. For now, please use bfgminer instead (link on front page of bitminter.com).

Red Fury is very sensitive and often gets stuck in a non-working state, even with bfgminer. You may be able to recover with the reset button on the device, or you may have to unplug it and plug it back in the USB port again to wake it up.

About blockchain.info showing too many Bitminter blocks, let me put it this way, I have sometimes seen their site get something right, but it's not often.

I emailed them about the problem, but they didn't reply.

According to them Deepbit is still finding several blocks per day, and half of P2pool's blocks are made by Bitminter. It would be funny if it wasn't confusing so many people.

TL;DR: blockchain.info data is usually wrong. Use this instead: http://blockorigin.pfoe.be/


Sounds like a network issue. When it cleared up the client grabbed a lot of work. Wouldn't have expected quite that much though. Also I've never seen it run at half hashrate like that after a network issue. Thanks for the report.


The website estimates your hashrate based only on accepted work. If you have a lot of rejected work or miscalculations (hardware errors) then that can explain the difference.


You'll need ASICs of course, to beat the electricity expenses. I think block erupter can still do that, but I guess it depends on your electricity prices. They can be hard to get at a price where you have a chance to break even, though. Run some scenarios through a bitcoin mining calculator before you decide what you want to pay for one. Or if you just want to try out mining and breaking even isn't that important, a cheap device like that should fit the bill.

Posting more should still work.


That's interesting. Does anyone know what the colors and blinking means? I've never seen any technical info on this device. I looked at the bfgminer source code to try and find out how it works.

It's based on what percentage of the work in the last 10 shifts was done by you. This was a routing error that affected some users and not others, so the few minutes it lasted it had some users mining and others not. This shouldn't affect things noticeably though if you are otherwise mining 24/7 since it was rather short. Some users took a while to switch back from their backups pools though.

To be exact the payouts are not calculated based on accepted proofs of work, but by score. Score = accepted proofs of work divided by difficulty. This slight complication is necessary to make the reward system completely safe from pool hopping during difficulty changes.

Reason for the bumpy ride we had:

It was a network issue that caused the majority of users to be unable to connect for a few minutes. Looks like we were down to 100 TH/s or so and the website was included in that so live stats went down as well. As data center engineers routed around the problem we came back to normal.

Screen capture looks normal. Red fury for some reason reports a lot of nonces that are wrong. I'll see if I can improve this in the future, filtering out some of them if they are supposed to be expected. Red fury support isn't quite 100% yet. There's no docs for this thing and it is a bit of a weird device.

Stale work rejected is normal up to 0.5% of your work. More than that and it's not normal.


#1 some users have reported this with Red Fury. So I recommend using bfgminer for now. The Red Fury support definitely needs more work.

#2 no more setup needed. Easy mode is for being able to set a high number of work submits per minute. That's for some high hashrate users who are worried about daily variance and want to mine at low difficulty.

Still? Or working now?

Not sure what that was. Miners unable to connect for a few minutes. Could have been a short network outage. Everything was working before I could look at it.

Apologies for that.

Yes, it's looking for ASIC hardware and not finding any.

https://en.bitcoin.it/wiki/Mining_hardware_comparison#ASIC