By Liam Frost
3 min read
Just a week after the last massive 51% attack, Ethereum Classic (ETC) is yet again under siege today, as an unknown party has reorganized at least 4,000 blocks in the blockchain, according to Bitfly, the company behind mining pool Ethermine.
Ethereum Classic developers urged all ETC services to “significantly raise confirmation times on all deposits and incoming transactions.”
The network saw a sharp and sudden influx of new computing power today, spiking the mining difficulty from around 56 to over 98 terahashes, data from mining-focused platform 2miners showed. Since blockchains usually strive to constantly retain the same time intervals between blocks (10 minutes in case of Bitcoin, for example), they automatically increase—or lower—the difficulty of discovering new blocks to match the current hashrate.
Ethereum Classic mining difficulty nearly doubled amid yet another 51% attack. Image: 2miners
Ethereum co-founder Vitalik Buterin suggested that ETC developers should just switch to proof-of-stake—an alternative consensus mechanism that relies on users staking their coins to maintain the network—and not on raw computing power used in ETC’s current proof-of-work algorithms.
A 51% attack is one of the most dangerous challenges a blockchain can face. During such assaults, a single party aims to seize 51%—or more—of a network’s hash power, which would grant the attackers control over the blockchain.
Among other things, this allows hackers to override and cancel their transactions, making it seem like they never happened, and spend their coins several times.
As Decrypt reported, Ethereum Classic suffered a massive 51% attack just days ago as the hacker reorganized the blockchain with his own malicious blocks by August 1, replacing the legit ones.
At that time, the attacker snatched over 800,000 ETC—worth around $5.6 million. To do this, he reportedly paid just about 17.5 BTC (roughly $204,000 today) for the computing power used in the attack.
Decrypt-a-cookie
This website or its third-party tools use cookies. Cookie policy By clicking the accept button, you agree to the use of cookies.