Some of the "missing" bitcoins were found in accounts that Karpeles forgot that he had previously told people he had control over. If he weren't the guilty party, wouldn't he have mentioned this upfront. Looks ultra-shady.
Karpeles IS unusually stupid (OK, let's say arrogant and naive). He claimed to have lost 2,000,000 bitcoins until people looked at the PUBLIC blockchain and found that he had previously had access to accounts where some of the "missing" bitcoins were still sitting. Then, all of a sudden, when the Japanese court threatened him with arrest, he was suddenly able to "find" and produce them.
This was a KNOWN and PUBLISHED flaw since 2011, along with clear instructions about how to avoid it. Any casual first-time programmer of bitcoin would have seen this when learning how to program bitcoin (it's on the Wiki: https://en.bitcoin.it/wiki/Tra...). Mt. Gox, having been around since 2010, could have not noticed I suppose, except that Gavin Andreson (the lead bitcoin developer) is on record as having warned them about this flaw multiple times. And it was brought up in a Bitcoin Foundation meeting where Karpeles was present.
The blockchain is PUBLIC. The vulnerability they mentioned is legitimate. They found 6000 successful attempts on the blockchain of double-spending a change transaction (all bitcoin transactions have an initial transaction and a change transaction, unless the amount matches perfectly).
These weren't related to known Mt. Gox addresses. How is this hard to understand that these guys know what they are talking about? Many of us in the bitcoin community could see this the very next day, as soon as we looked.
I used to work at an auto parts store where someone was stealing from the registers. Since we had just hired a guy back after going to jail (presumably for something he didn't do), all eyes were on him. It was a slow night, so my co-worker and I took a look at the shift logs and who worked 1-2 shifts before the money was found missing (because it had safe drops, you couldn't always tell the next shift).
It took us about 20 minutes to find the culprit. It was totally easy. So this is complete BS.
Um, no. Transaction malleability is easy to find on any miner's log. I am sure these guys are correct.
The people that left their coins sitting on Mt. Gox's servers instead of getting them off immediately? Yes, those people are unusually stupid.
The people that are buying Lambroghinis ( http://articles.latimes.com/20... ), apartments ( http://www.uproxx.com/webcultu... ) and even castles in Estonia ( http://thebitcoinnews.co.uk/20... ) for mere pennies on the dollar don't seem very stupid.
Some of the "missing" bitcoins were found in accounts that Karpeles forgot that he had previously told people he had control over. If he weren't the guilty party, wouldn't he have mentioned this upfront. Looks ultra-shady.
Karpeles IS unusually stupid (OK, let's say arrogant and naive). He claimed to have lost 2,000,000 bitcoins until people looked at the PUBLIC blockchain and found that he had previously had access to accounts where some of the "missing" bitcoins were still sitting. Then, all of a sudden, when the Japanese court threatened him with arrest, he was suddenly able to "find" and produce them.
This was a KNOWN and PUBLISHED flaw since 2011, along with clear instructions about how to avoid it. Any casual first-time programmer of bitcoin would have seen this when learning how to program bitcoin (it's on the Wiki: https://en.bitcoin.it/wiki/Tra...). Mt. Gox, having been around since 2010, could have not noticed I suppose, except that Gavin Andreson (the lead bitcoin developer) is on record as having warned them about this flaw multiple times. And it was brought up in a Bitcoin Foundation meeting where Karpeles was present.
The blockchain is PUBLIC. The vulnerability they mentioned is legitimate. They found 6000 successful attempts on the blockchain of double-spending a change transaction (all bitcoin transactions have an initial transaction and a change transaction, unless the amount matches perfectly).
These weren't related to known Mt. Gox addresses. How is this hard to understand that these guys know what they are talking about? Many of us in the bitcoin community could see this the very next day, as soon as we looked.
Nobody has seen Karpeles lately, BTW.
Every natural disaster results in hundreds of fake charities being set up to collect donations.
You mean like the Red Cross? Where they collect billions and give virtually nothing.
I used to work at an auto parts store where someone was stealing from the registers. Since we had just hired a guy back after going to jail (presumably for something he didn't do), all eyes were on him. It was a slow night, so my co-worker and I took a look at the shift logs and who worked 1-2 shifts before the money was found missing (because it had safe drops, you couldn't always tell the next shift).
It took us about 20 minutes to find the culprit. It was totally easy. So this is complete BS.
Dissolved ocean fossils don't count?
Sounds like Target should start taking bitcoins. No information to lose.
Actually, the EA CEO was pretty torn up about it, but yeah, bottom line means way more.
If you believe strongly enough, you'll switch to AMD or ARM exclusively. I doubt it though.
There's no hate campaign against Eich.
Ha ha ha ha ha ha ha. Did you miss the internet that day?
Actually, the scariest part I'm seeing is all the PILOTS saying, "No way would I do that. Have you SEEN those other pilots?"
How much to rent a car in Durango or Phoenix? Because they sure as heck are not going to have public transportation worth anything.
Would you be against a 1 minute delay? Or 30 seconds?
This was the example given on the 60 Minutes piece.
They get around it by looking at OTHER PEOPLE'S orders (as if that's better).
I think a 30 minute or 1 hour limit would take care of your concerns.
And Sintel is virtually already in the public domain, except for attribution.
And there's no way for you to recover any lost wages? That's awful.
Typical Microsoft security... :(
Actually, it says Hunter2 for me...
So, can we figure out why that Mars mission failed? And if so, maybe we should release the code ahead of time so people can help look for bugs.