51% Attack Bleeds More Than $5M from Ethereum Classic
cointelegraph.com
cointelegraph.com
I imagine if such a case ever goes to court its going to be very interesting, because for the government, this should be like being stuck between a rock and a hard place. Acknowledging this as "theft" kindof undermines their agenda to kill off alternative currency.
There is also another dimension to it. "Double spending" conceptually seems very similar to the government printing money, devaluing the dollar.
But who is selling anything for Eth?
> Acknowledging this as "theft" kind of undermines their agenda to kill off alternative currency.
Whose agenda?
Governments generally have no interest in alternate currency systems that are not under their control, taking off. So far, crypto currency has been flying under the radar and the ones that have broad support from financial institutions go against the very idea of Bitcoin and Etherum, i.e. they are not providing much of the benefit that supporters of crypto currencies are interested in.
Total Coinbase fees already went over Intercontinental Exchange fees in the last cryptocurrency bubble (because of the large margins).
And it would be trivial to convict on this - they deposited huge sums into exchanges, traded them for another currency, then double spent the deposit
It's just theft
Imagine a webpage with a box to paste a transaction you want reversed. It will quote you how much it costs to undo that transaction, and if you're happy you pay that amount.
The service would make money if multiple people wanted transactions reversed over the same time window, since the 51% hashpower cost only has to be paid once, even though you get paid twice.
Clearly some exchanges weren't following that rule!
Waiting for a certain number of blocks is only to reduce the probability of natural fork eliminating the transaction (by eventually outgrowing the fork you included your transaction into) to infetesimally small.
4000 blocks is also, I think, extremely deep into the chain. As I recall, bitcoin exchanges default to like 6 blocks before confirming?
At least, this was from my readings into bitcoin -- not sure if ethereum changes that equation, but im fairly positive it doesnt.
If you are verifying a transaction of a given value, you would be stupid not to wait the dollar value of the hashpower required to reverse the transaction. If you run a service and someone could sign up for multiple accounts, you should take that into account too...
Detecting the attack or vulnerability to it is easy in smooth difficulty increasing proof of work systems by looking for spikes in difficulty... But waiting for too long is not acceptable.
This attack was against Ethereum Classic, which has a block time of 13 seconds. 4000 blocks ≈ 14 hours.