That's up to you. You can use multiple workers if you want separate statistics for them. If you don't need that, just use the same worker.

This is not possible currently. I am thinking about some ideas along those lines though, for the future.

No, and it probably won't be implemented either. Just use some random words/characters as user name if you want to be anonymous.


This is planned, but not ready yet.

Sometimes there is a conflict between database transactions and one of them has to start over. But sequence numbers are never reused. This way sequence numbers end up with "holes" in the sequences. I may remove shift numbers from the shifts list, but they are sometimes useful to be able to easily refer to a specific shift.

TL;DR: Yes, it's a glitch in the Matrix.

Sounds like the java plugin is not working in your browser. Could you try starting from command line instead?



I did run it on a raspberry pi a little bit for testing. Which operating system did you install on your pi?


For that little data it looks pretty even. If you want a thorough analysis have a look at the one Organofcorti did: http://organofcorti.blogspot.com/2013/05/131-bitminter-and-luck.html


If you are still having problems please contact me through the contact page at the website and I'll look into it.

Looks like an attack was able to cause a few minutes of instability. Sorry for that. We were quickly back to mining though.

The approximate mint speed shown in BitMinter client is just that, an approximation. Bitcoin mining is like a lottery. How often we find a block, and earn bitcoins from that block, is random. Each hash you process is like a lottery ticket. Each hash has a (very low) chance of producing a block. You get paid with coins from a block whenever a block is found by someone mining in the pool. Your share of the income from a block is determined by the amount of work that you did in the most recent 10 shifts at the time the block is found.

Because of this, your daily income will vary with luck. That's often referred to as variance. There may also be some hours between two payouts if we are having bad luck and no blocks are found for a while.

In addition to that there is a delay from the time you do some work until that work is fully paid. The work you do is registered in a shift, and then that work is credited with income from new blocks we find until its shift is no longer among the 10 latest shifts. This takes a few hours. If you turn off the prepay perk then there is an additional delay having to wait for blocks to confirm, which takes about 20 hours.

So, assuming you have prepay on, if you do 24 hours of work and then look at the results, then only some of that work has been fully paid. The remaining work is still receiving pay, even if you stop mining. Needless to say that is not going to look very profitable, when you are looking at all the work you did but only part of the pay you are going to receive.

Comparing pools by how much you get paid for 24 hours of mining is pointless. The comparison becomes "which pool has the best luck today?" You can't use that data for anything. The luck a pool has today has no influence on its luck tomorrow. Believing that it does is called "gambler's fallacy" which you can ready about on wikipedia:

  http://en.wikipedia.org/wiki/Gambler%27s_fallacy

If you want to know how BitMinter's payouts have been over time you can read Organofcorti's very detailed analysis here:

  http://organofcorti.blogspot.com/2013/05/131-bitminter-and-luck.html

That's what it is. Thanks. I will have an update for this soon.


This is implemented and working but has no web interface yet for choosing the target number of submits per minute. The default is 20 proof of work submits per minute. Use the contact page on the website to leave me a message and ask for a lower number and I can set it for you manually. If you have multiple workers let me know which one(s). I hope to have time to get this on the website soon.


That's a broken browser plugin. It's fairly common with Firefox and Chrome that some plugins will break webpages. They sometimes cause a duplicated URL as you can see from the error message. Try running your browser with plugins disabled or try a different browser if you have multiple browsers installed.

I would recommend removing any plugins that try to "enhance" webpages and end up breaking them. You don't want that.

Ah. That's probably an oversight. Anyway, it won't be an issue once cpu mining is disabled.


Does it recover and continue mining after that or get stuck? Are there any other errors shown in the log, like network errors?

CPU mining will be removed in a future release. Just don't click on the start button for the CPU and it won't start. If you click the button to start all devices it will start all devices except the CPU (unless you had the CPU running earlier).

No, the price is very low compared to the USB block erupter group buys. ROI would be much easier with BFL units.

The actual problem is the order backlog. While the units are much faster and cheaper per Ghps than the block erupters, if you order today it will take a while before you receive the product. That's how ASICminer can charge very high prices for very slow units - the competition just isn't able to deliver enough units.

There are no missing blocks. Just like there are no "extra" blocks when we have lucky short rounds.

Bitcoin mining is like a lottery. Sometimes you find blocks quickly with only a few hashes (lottery tickets) and sometimes it takes many hashes.

Luckily we found a couple quick blocks after that 26 hour block, which helps even out the bad luck we just had.

If the variance makes you uneasy then you can mine in a PPS pool instead. You'll have high fees, no income from transaction fees, no namecoin income. In short, you will lose a lot of money. But you won't have any variance at all. The same (very low) payouts every day.

Maintenance took a bit longer than expected. I'm on vacation with a less than perfect internet connection. Sorry about that. This took about 40 minutes for mining and 5 minutes more for the website.

All systems looking good.

Looks like it was a small ddos attack. Everything looking stable now.

Not yet. Seems network was down for a moment. Looking into it.

Maintenance tomorrow, monday 2013.07.15 at 20:00 UTC. Expected downtime 10-20 minutes.

Sorry for the short notice.

Yep, support for failover pools is coming.


That's a crash in the AMD graphics drivers.

amdocl64.dll = AMD OpenCL 64 bit drivers

AMD drivers have been pretty rotten in 2013 so far. You could try their latest beta driver, some users had luck with that.

Sometimes MintBot reports the block before the income has been registered, and it shows zero. I'll see if I can make it report the blocks only after the income is registered.

Last block shown in the BTC luck graph is height 246333. Looking at the blocks list the last block we found is 246333. That looks correct.

Not yet, but coming soon.