If MtGox attempted to make a transfer to the address, but that transfer failed as a double spend because their wallet database is corrupt (and that appears to be the consequence of the bug they are having) then these addresses have been published on the net.  It looks like somebody is occationally sending dust amounts of bitcoin to many addresses, perhaps in the hope that the receivers' wallet will combine many of these micropayments from different addresses into a single payment.  This would help determining which bitcoin addresses belong to the same owner. 

There have been many reports of these strange micropayments, and the only theory I have seen is that it is to try to break some of the anonymity of bitcoin by tricking our wallets into revealing which addresses that belong together.

Spooky, but probably not related to MtGox.

Since litecoin is a clone of bitcoin, they probably have the same problem.

Note that although this is technically a flaw in the bitcoin protocol, it is not a serious one, at least not once it is known.  It just means that before you conclude that a transaction did not make it into the blockchain, you have to check the blockchain a bit more carefully.

This really makes it looks like closing withdrawals was the right thing to do, at least until the problem was identified.  They should be able to fix it in their own software.

That is perfectly safe - I have done it several times.

OK, it had to be bad to be more insecure that no GA

What happened to Google Authenticator 2FA?

The last few times I was logging in, I was no longer asked for my GA code.   

Firstbits has been disabled for a few months, apparently it overloaded a database.  I hope it comes back soon.

I do care, there is just so little I can do about it (outside the voting box every fourth year).  And is has no practical issues for me, I really doubt the NSA will steal my bitcoins, and I don't use them for anything they would be interested in.  But it does make me angry.  Very angry!.   And my own government seems to think it is OK the NSA (and who knows what other oh-so-friendly foreign agencies) spy on us.     

The main practical problem is if NSA introduces security holes that other evil hackers abuse. 

The main real issue is that by embracing the methods of the totalitarian state, we are dismantling our democracy.  Replacing my iPhone with an Android will not help 

First, you check that the downloaded file match the SHA-256 checksum in SHA256SUMS.asc

Then you check that SHA256SUMS.asc itself has not been tampered with

You are right.

And really the ICBIT futures are USD futures settled in BTC, but they are "marketed" as BTC futures, so "BUY" buys BTC and sells USD.

I agree it is confusing - but in the end it is probably less confusing that buying is buying BTC just like everywhere else.  A choice between two evils.
 

No, buying something for 10 USD TODAY is betting that the price of USD is going down.  If USD are cheaper in the future, you would have got fewer bitcoins in the future, and you keep the rest.

Whoah!  That caused your market to crash.   

OK, this is not a dramatic change, and it does not look like it affects us users in any bad way - just a bit less manipulation, which is good for most of us, I guess. 

Try running bitcoind or bitcoin-qt in the guest as well.  Just be absolutely sure not to run it simultaneously on the host and guest if you share the directory!

They are extremely well connected, probably thousands of connections to the network, whereas you only have a dozen or so.  So it is likely that a miner that does not care about the fee is listening to what blockchain.info is transmitting, even if the majority of the network does not propagate it.

(I am speculating here)

IF you drop your wallet, don't drop it completely.  Just move the file somewhere else, then if everything else fails you move it back, and everything should be OK.

But first:  Look at your wallet with Wallet Properties.  Are you sure that none of the three check-boxes are selected.  They are called "Hide empty", "hide change" and "hide unused".  If any of them is selected, try unselecting it.

You might want to repost this in an Ubuntu thread (or create one in the Armory sub-forum).  Since this is a thread about compiling on Mac OS X the Ubuntu or Linux experts are less likely to see it.

You know it is corrupted by the client complaining that it is so.

And no, you do not lose coins.  The wallet is not affected (although you should always have a backup), the worst that could potentially happen is that your client "fortgets" you have the coins, or think you have too many (forgets you have spent some).  But rebuilding the database will fix that, since your bitcoins are not stored on your computer but in the blockchain.

Hi etotheipi and co.

I just want to point out that the Bitcoin-Qt developpers are looking at a levelDB problem that could also affect Armory:
https://bitcointalk.org/index.php?topic=337294.0


Edit: As goatpig points out, I mean affect Armory in OS X.

I think that is a joke - it means the site is down.

Such things were funny back when BTC were essentially worthless, but not any more.  Our sense of humour is inversely proportional to the amount of money we have placed on a web site.