Not really a problem when you use Scala. If you're into programming then check out Scala today. You won't regret it.

Mining server software was updated and appears to be running very well.

Sorry for the instability issues right now. I've found two weaknesses that can cause very high CPU and memory usage on the server when ddos attackers are pounding it the way they are lately. I'm working on fixing both now and will deploy the fixes ASAP. That means you'll be disconnected one more time for the update, without a maintenance time announced ahead of time, but this has to go in quickly to make the service more stable.

More to follow as the fix is deployed.

That's only superstition. Besides, bitcoind wasn't restarted.

Good to hear it worked with Linux Mint 16

This is a strange bug. I guess it only happens under certain Java configurations. I'll do some further testing when I have time.

Looks like about 200-300 users are blocked by the anti ddos currently. If you are one of them, you should be able to connect again within a minute or two. Apologies for the inconvenience.

As a rule of thumb you can set the difficulty to your hashrate in GH/s divided by 1.4. That's probably 1.x in your case. However the pool minimum is currently 2. You could just leave it at default. Setting a minimum difficulty is mostly useful for high hashrates like 100 GH/s and above.

Some more info on worker difficulty: https://bitcointalk.org/index.php?topic=27062.msg3142713#msg3142713

Wow, 4 blocks in a row on the blockchain today.

Everything should be running smoothly now. If you have issues there are two types of IP based filtering in use. There's a botnet ban list where IPs sit for some time. And then there is the anti ddos which may accidentally filter you along with attackers during an attack. We're working to improve on this. This should only last a few minutes before you can mine again though. If you are unable to mine for hours then you could be on the botnet ban list, or it could be a different issue entirely. In that case use the contact form ("contact" menu) on the website and I'll see if I can figure out what the problem is.


Hehe, this gave me a good laugh. That's exactly what it's like.

Banning botnets and fending off their attacks. Bit of a bumpy ride at the moment. But looking better already.

To botnet herders: connecting thousands of cpuminer instances using getwork from 1 IP is no better than from thousands of IPs. It still causes a lot of load for almost no effect, and you will still get banned. Also, advice on illegal botnet activity: earning 0.01 BTC per year is not worth going to jail.

How difficulty increases affect your mining income:

http://bitcoin.stackexchange.com/questions/16526/how-does-a-difficulty-increase-affect-a-miners-income


Let me know if you find out whether it works with the latest Bitminter client or not.

Mining service restart... will only take a second or two.

Are you still having this issue? If so, could you send your IP address to operator@bitminter.com, then I can look into it on my side. Thanks.

Yep. And if you go back in the shifts list you can see the shifts getting longer right on the point where the difficulty changes.


In the latest version of Bitminter client I made a fix for the Chili firmware BFL-incompatibility, but I couldn't get anyone to test whether it works. Worth a try.

Of course there had to be one system that works differently from everything else so that there is no one method you can rely on everywhere. Brilliant.

First open the Java Control Panel. There are various ways to do this on various operating systems. One technique that works on every OS is from the command line. Open a command prompt (Windows) or Terminal window (Linux, Mac) and type This opens both the Java Control Panel and the Java Cache Viewer. Simply close the cache viewer and you are left with the control panel.

In the control panel select the "advanced" tab and go down to "shortcut creation". This is usually set to "prompt user if hinted". This means that if the application hints that it likes to have a shortcut then a dialog will pop up asking if you want a shortcut. You'll need to change this to one of the "always" options or the one "never allow" option. "Always allow" means you get a shortcut for every webstart application you run. "Always allow if hinted" means you get shortcuts for every webstart app you run that hints that a shortcut should be created. Finally "never allow" means that shortcuts are never created.

Thanks for the support, guys.

We are back to over 9000 connected users. Looking good

We are under ddos attack again. Some users are experiencing problems connecting because they get filtered along with the attackers. We are working on improving the filtering right now to prevent this from happening. Working on this right now.

We are under ddos attack again. Some users are experiencing problems connecting because they get filtered along with the attackers. We are working on improving the filtering right now to prevent this from happening. Working on this right now.

That's blockchain.info mistakenly thinking the block was created by Bitminter just because it was relayed through one of our bitcoin nodes.

blockchain.info needs to learn that in a peer-to-peer network everyone are relaying data all the time. If they see a block being relayed through a certain bitcoin node, it doesn't mean anything.

It's possible you got filtered along with the botnet. In that case it should not last more than a couple minutes.

Unlucky day today too, yes. Hopefully we find more blocks tomorrow. Should be 3 payouts though, not 2.