Certainly they are not telling the truth about the transaction malleability. They have now dug their feet in on that explanation but it does not make sense given what we know about transaction malleability (the kind they are talking could not possibly have cause 850,000 bitcoins to disappear from allegedly cold storage without them noticing, and probably not without some social engineering.)
It seems likely that if the bug was involved somehow, it was because an intruder performed an attack from inside Gox . How else would they also be able to get fiat deposits out of Mt. Gox? Wouldnt that require initiating bank transfers?
It doesn't make sense as an explanation, especially given that we now know that some Russian clowns also had database access.
If you had a verified account you could ask for any limit you wanted up to 10k BTC, with a trusted account I think there was no maximum— I've talked to people who say they had 50k limits.
There was a 200 BTC maximum per withdraw however, at least in recent times.
> as the consistent Gox bug was only triggered by 0.8.0 being released
Even that wasn't consistent, only ~1% of signatures were invalid DER encodings with their code.
Wsn't aware of that, I only ever saw 200BTC being mentioned. Did Mt Gox seriously keep 10,000BTC+ in their hot wallet for this to work, or were manual withdraws like a bank where you make a cash request for the next day?
That's certainly believable. My limit was 10k, IIRC, and I haven't used Mt. Gox since 2011.
Big Red Shoes, Inc.? ClownCarDB?
Clowns.
At what point, given normal business conditions, would you need to hold 100% of deposits? You only need enough to cover withdrawals; ignoring the MtGox issues 60% seems quite reasonable.
The only time you'd need to worry about 100% is if you're anticipating a total run on deposits or you're going to close the bank.
At the point where you're not a lending bank, which Gox is not. They shouldn't have been running a fractional reserve at all.