It works out to having 5.98% of all bitcoins that have been created as of today, have been stolen in this theft. That is a GIGANTIC haul, it has to be in the top 3 biggest robberies ever (and of course, due to the crazy price fluctuations, may become the biggest robbery given enough time). I wonder if they'll ever figure out who was behind this.
Starting Score:
1
point
Moderation
+3
Interesting=3,
Total=3
Extra 'Interesting' Modifier
0
Total Score:
4
(Score: 1) by tftp on Wednesday February 26 2014, @01:54AM
I wonder if they'll ever figure out who was behind this.
You don't have to be Sherlock Holmes to realize that it's physically impossible for a major financial institution to run open loop, without ever checking the ledger, for several years. Nobody is that dumb. This means that they knew it all along, but continued to disburse BTC as if there is no tomorrow. Cui bono?
Completely agreed. The idea they were not auditing there own ledger is just too much to be believed. It is just amazing they kept the lie running for so long. It is something that should have been caught years ago. It'll be interesting to see what the Japanese authorities determine, though that might take some time.
If I understood it correctly, the problem was that they used a hash to identify transactions that is not the same hash that they sign to authorize transactions, so people could modify non-critical parts of a transaction and for the block chain the transaction would go through but to the exchange it seemed that the transaction hadn't happened, so they would retry the transaction.
As you said, it is very unlikely they wouldn't notice this if it had been going on for years. Also it sounds like a bug that is relatively easy to fix, so why would they not fix it if they knew about it? And why are they calling it a core protocol problem when it is in fact a problem of the exchange software? Are they really that incompetent?
Shouldn't it be possible to spot the retried transactions in the block chain? I assume they would have the same amount and destination address as the forged ones. Then it would be possible to determine an upper bound for how long this flaw has been exploited and how many bitcoins were taken.
I suspect you are very much correct in your understanding of the problem. You should be able to analyze the blockchain for these occurances. However you'd first need to identify all of the wallets mtgox uses to send out btc's. You could analyze the entire blockchain, but I suspect you'll find a shockingly large number of false positives due to things like pool payouts where you can setup your threshold on when they payout or even people manually moving the same amount of bitcoins over and over. I've seen some automated/bot bitcoin sellers that slowly trickle out sales of the same size over and over again (with the purpose of slowly selling btc's so to not impact the market price).
to the exchange it seemed that the transaction hadn't happened, so they would retry the transaction.
Imagine that you pay for rent with checks. Periodically the landlord calls you and says that he hasn't received the check. What would you, as a sane person, do? Would you simply cut another check and mail it in, without bothering to look if the original check had been paid? Or, perhaps, you will make sure that the double payment will not occur?
If the exchange felt the need to retry payments, this shows that the BTC system (in their opinion!) is fundamentally broken. It is unacceptable to submit a payment and then guess if it went through or not. (Especially if you haven't added the bribe to miners, also known as the voluntary fee.) Banks ensure that your payments are atomic, reliable, and verifiable at many checkpoints - and all that happens entirely for free to you. If BTC is not as reliable as a bank, who would need it? Now Mt. Gox tells us that they thought that the BTC network is not reliable. Is it true (and BTC is bad) or is it a lie (and then Mt. Gox is responsible for the loss?)
I wonder if they'll ever figure out who was behind this.
Sure, it's only a matter of time before all those Bitcoin dye packs [wikipedia.org] explode. Just look for somebody whose whole neighborhood is covered in millions of tiny red bits.
LOL. Yes, I realize that. I was just thinking with all of the transaction logs that mtgox would have, plus their KYC and AML information they have on each customer, they'd have something to investigate.
The problem is only supposed to be an issue when a customer pulls bitcoins out of the exchange. Then after they get the bitcoins, they use that TM issue to modify there transaction info so it looks like they never got the bitcoins. Later on, they contact the exchange and say they never received there coinage, and to please fix/resend. Supposedly mtgox was sending out, effectively twice the amount of bitcoins to them.
They should have a clear way to search what customers complained they never got the coins, where they resent them twice. And with the KYC (know your customer) they should have detailed information on them. All of this assumes they, mtgox, weren't just skimming off the top this entire time.
(Score: 4, Interesting) by tynin on Tuesday February 25 2014, @11:36PM
It works out to having 5.98% of all bitcoins that have been created as of today, have been stolen in this theft. That is a GIGANTIC haul, it has to be in the top 3 biggest robberies ever (and of course, due to the crazy price fluctuations, may become the biggest robbery given enough time). I wonder if they'll ever figure out who was behind this.
(Score: 1) by tftp on Wednesday February 26 2014, @01:54AM
I wonder if they'll ever figure out who was behind this.
You don't have to be Sherlock Holmes to realize that it's physically impossible for a major financial institution to run open loop, without ever checking the ledger, for several years. Nobody is that dumb. This means that they knew it all along, but continued to disburse BTC as if there is no tomorrow. Cui bono?
(Score: 1) by tynin on Wednesday February 26 2014, @02:05PM
Completely agreed. The idea they were not auditing there own ledger is just too much to be believed. It is just amazing they kept the lie running for so long. It is something that should have been caught years ago. It'll be interesting to see what the Japanese authorities determine, though that might take some time.
(Score: 1) by mth on Wednesday February 26 2014, @04:42PM
If I understood it correctly, the problem was that they used a hash to identify transactions that is not the same hash that they sign to authorize transactions, so people could modify non-critical parts of a transaction and for the block chain the transaction would go through but to the exchange it seemed that the transaction hadn't happened, so they would retry the transaction.
As you said, it is very unlikely they wouldn't notice this if it had been going on for years. Also it sounds like a bug that is relatively easy to fix, so why would they not fix it if they knew about it? And why are they calling it a core protocol problem when it is in fact a problem of the exchange software? Are they really that incompetent?
Shouldn't it be possible to spot the retried transactions in the block chain? I assume they would have the same amount and destination address as the forged ones. Then it would be possible to determine an upper bound for how long this flaw has been exploited and how many bitcoins were taken.
(Score: 1) by tynin on Wednesday February 26 2014, @10:28PM
I suspect you are very much correct in your understanding of the problem. You should be able to analyze the blockchain for these occurances. However you'd first need to identify all of the wallets mtgox uses to send out btc's. You could analyze the entire blockchain, but I suspect you'll find a shockingly large number of false positives due to things like pool payouts where you can setup your threshold on when they payout or even people manually moving the same amount of bitcoins over and over. I've seen some automated/bot bitcoin sellers that slowly trickle out sales of the same size over and over again (with the purpose of slowly selling btc's so to not impact the market price).
(Score: 2) by tftp on Thursday February 27 2014, @03:29AM
to the exchange it seemed that the transaction hadn't happened, so they would retry the transaction.
Imagine that you pay for rent with checks. Periodically the landlord calls you and says that he hasn't received the check. What would you, as a sane person, do? Would you simply cut another check and mail it in, without bothering to look if the original check had been paid? Or, perhaps, you will make sure that the double payment will not occur?
If the exchange felt the need to retry payments, this shows that the BTC system (in their opinion!) is fundamentally broken. It is unacceptable to submit a payment and then guess if it went through or not. (Especially if you haven't added the bribe to miners, also known as the voluntary fee.) Banks ensure that your payments are atomic, reliable, and verifiable at many checkpoints - and all that happens entirely for free to you. If BTC is not as reliable as a bank, who would need it? Now Mt. Gox tells us that they thought that the BTC network is not reliable. Is it true (and BTC is bad) or is it a lie (and then Mt. Gox is responsible for the loss?)
(Score: 1) by CaptainK on Wednesday February 26 2014, @02:47AM
just out of curiosity and a little off the topic...do they even know who created bitcoin?
Your imagination is your only limitation to creation.
(Score: 1) by tynin on Wednesday February 26 2014, @02:09PM
Nope, no one knows, and there has been a LOT of speculation / leg work / investigations, by likely thousands of people for a few years now.
(Score: 3, Funny) by TheloniousToady on Wednesday February 26 2014, @04:55AM
Sure, it's only a matter of time before all those Bitcoin dye packs [wikipedia.org] explode. Just look for somebody whose whole neighborhood is covered in millions of tiny red bits.
(Score: 1) by tynin on Wednesday February 26 2014, @02:20PM
LOL. Yes, I realize that. I was just thinking with all of the transaction logs that mtgox would have, plus their KYC and AML information they have on each customer, they'd have something to investigate.
The problem is only supposed to be an issue when a customer pulls bitcoins out of the exchange. Then after they get the bitcoins, they use that TM issue to modify there transaction info so it looks like they never got the bitcoins. Later on, they contact the exchange and say they never received there coinage, and to please fix/resend. Supposedly mtgox was sending out, effectively twice the amount of bitcoins to them.
They should have a clear way to search what customers complained they never got the coins, where they resent them twice. And with the KYC (know your customer) they should have detailed information on them. All of this assumes they, mtgox, weren't just skimming off the top this entire time.