About 30% of users currently have problems connecting to the mining server. I'm looking into it.

Upcoming maintenance 17/18 Feb 2014:

Upgrade one, 17 Feb 23:00 - 18 Feb 05:00 UTC. Expected mining downtime 0-10 minutes. Website downtime 15-30 minutes.

Upgrade two, 18 Feb 04:00-08:00 UTC. Expected mining downtime 5 minutes. Website not affected.

I'm sorry for the inconvenience this causes. Hopefully this maintenance will be smooth and barely noticeable.

Which serial port are they on? Could you try "devices" -> "probe specific port" in the menu to see if that is able to pick them up?


Which internal devices are you trying to run?

Graphics cards will pop up automatically if they support OpenCL. CPU mining has been removed.

New Bitminter client beta with Antminer U1 support: https://bitcointalk.org/index.php?topic=31163.msg5170249#msg5170249

Overclocking and LED blinking not ready yet, but I didn't want to delay it any longer.

BitMinter client v1.5.0beta1 is ready for testing.

New:

• Add support for Antminer U1
• Fixed a memory leak that could happen when mining on BFL ASICs. This could slow down the program and eventually make it lock up completely.
• Display approximate earnings per month rather than per day

Please check it out:


Edit: Setting the Antminer clock frequency or blinking the LED not yet supported. I hope to have that ready soon.

We're back again. Sorry about that. Someone trying out new ways to mess with the server.

There's an issue with the mining server. I'm in touch with the data center, trying to resolve this ASAP.

Sorry about that. You should be reconnected now?

The pool has not been hacked. So the "worst security ever" must be somewhere else.

If your computer has been compromised you need to wipe everything. Back up your documents (not programs!) and reinstall the operating system. Then, logging in from a clean computer, change the password on every website you use.

It's a good idea to enable 2-factor authentication as a security measure. See instructions here: https://bitcointalk.org/index.php?topic=27062.msg4892396#msg4892396

Note that 2-factor auth will not save you if your computer has been compromised. It only makes the job a little bit more difficult for the hacker.

You MUST keep your computer secure. There is no way to make it safe to log in using a compromised computer. If you do online banking with malware on your computer, then your bank account can be cleaned out. Yes, even with 2-factor authentication. When you are typing in the one-time passwords/codes you are giving them to the hacker who is controlling your computer.

I can deal with mutated transactions, and I have no plans to shut down and wait for a fix. I agree that transactions are malleable today, and to run a bitcoin service today you will have to deal with that. I also agree that this is a difficult thing to fix in a good way. So it may take some time until we see a good solution. I never disagreed with any or that and I never said I, personally, had problems dealing with malleability.

What I have a problem with is all the people saying there is nothing wrong with bitcoin. Malleability is not a bug, it's just the way bitcoin works. And if it causes problems for you then the issue is your low IQ, not malleability. There are plenty of knowledgeable people saying these and similar things. In my opinion people acting this way can harm bitcoin more than malleability itself.

By the way, while we have these booby traps waiting to cause disasters for unsuspecting newbies; wasn't there someone working on a best practices guide/document for bitcoin?

Bitminter client automatically connects to the Bitminter pool.

Hardware for mining bitcoin today is ASIC: https://en.bitcoin.it/wiki/Mining_hardware_comparison#ASIC

Lol. I must admit, I did not do my research there. Apple actually responded exactly the same way the Bitcoin community is responding about malleability. I guess it's a normal human reaction. If someone says something negative about something you love then they are always wrong. Per definition.


You just chose B but wrote the text in a different way. The fact that the transaction identifier cannot identify a transaction is a bad thing. It doesn't matter what you call it. I'm pretty sure it is a bug and unintentional. But even if you call it a feature and say it is what Satoshi intended all along, that's all irrelevant.

bitcoind gives you a txid when you send coins. bitcoind has "gettransaction <txid>" to look up transactions. This being broken means that it is all there as a trap to cause you grief. And as a great tool for social engineering to steal your coins. What you are basically saying is that you want bitcoind to contain broken tools so that people will have problems and lose lots of money, and then you can later laugh at them and call them stupid. I don't think that's a good future for bitcoin.

Insisting that something bad is good - that's NOT how you build a good product.

Giving people a broken tool and calling them stupid when they struggle to use it - that's NOT how you promote a product.

Moving users back to the normal server. Hashrate etc may look wacky for a couple minutes.

Switched to backup server. DNS propagation may take a couple minutes, but you should be mining again in a moment. Will switch back once the main server is back up.

There's an issue with the mining server right now. I'm looking into it.

This was my point. Many would disagree with you.

It's like the time when one of the iPhone models had antenna problems. Apple told people there was nothing wrong with the phone, the problem was actually the low IQ of the users, they didn't understand they needed to hold the phone a certain way for it to work. Oh, that's right, Apple never said that.

Me: I'd like to send some coins.
bitcoind: Sent in transaction ABC123.
Me: How is transaction ABC123 doing? Any confirmations yet?
bitcoind: Are you making things up? There's no such transaction.
Me:

(The transaction did go through but is now called XYZ789)

Now you have two options:

A) Bitcoin isn't perfect, but we can make it better.

B) Bitcoin is perfect. You are the problem. YOU'RE STUPID!

I see many people already chose attitude B.

It's the wrong choice.

Yeah. They know they won't get any more sleep that night otherwise.


Are you getting a lot of rejected work or hardware errors (miscalculations) ? I'm not sure if the blade web interface shows hardware errors?

Maintenance February 11, 04:00-08:00 UTC. Short downtime (max 5 min) expected. Apologies for the short notice.

In case of problems my cell phone plays a loud air raid siren. It wakes the entire neighborhood.