MTGOX PROBLEM - Sold BTC was never credited USD - Check YOUR History

[mike85123]

This happened when MTGox was being DDOS'd the other day. I have emailed them and they have said they are looking into it, but still no USD.

I sold BTC in 4 different transactions. On the BTC History, it shows 4 transactions going out. But on the USD History, it only shows 3 transactions being credited.

In the BTC history:


In the USD history:


As you can see, I was credited USD for the transactions ending in 332, 479 & 182, but not for the one ending in 747.

I WOULD CHECK TO MAKE SURE THAT ANY TRADES IN YOUR ACCOUNT WERE CREDITED PROPERLY AROUND Thu 25 Aug 2011 12:14:41 AM EDT. I HAVE A FEELING THAT IF THIS HAPPENED TO ME, IT HAPPENED TO A LOT OF OTHER PEOPLE

They also still need to credit me for my free yubikey, because the coupon code for it to be free didn't work. Still waiting on that from 3 days ago....  Both of these issues seem like issues that should be taken care of ASAP, yet Gox is taking their fucking time with mine (and likely your) money.

[1715407888]

1715407888

[1715407888]

1715407888

[1715407888]

1715407888

[1715407888]

1715407888

[1715407888]

1715407888

[Villem Anton]

Also mtgox have a stupid way to report transactions. There should be only one history where you have all of the following

Trade:
  Time
  Price
  Currency
  Volume (amount in BTC)
  Amount in Currency
  Fee BTC
  Fee Currency
  Balance BTC
  Balance Currency

Now it is very hard to check if it looks right. I wonder if they ever traded with a real broker...

[smurfix]

Ouch. Somebody should teach them about this novel database concept called a "transaction".
DDoS or not, it should simply be impossible for something like this to happen.

[MagicalTux]

Ouch. Somebody should teach them about this novel database concept called a "transaction".
DDoS or not, it should simply be impossible for something like this to happen.

We use transactions. Somehow mysql committed on its own some transactions while it shouldn't have. We have fixed this and added some checks to prevent similar behaviour.