Ethereum Classic Labs Sought Hash-Rental Oversight After Repeated Chain Attacks

Ethereum Classic Labs said on August 31, 2020 that it had launched an initiative to involve law-enforcement agencies and global regulators in oversight of hash-power rental markets. The announcement followed a third deep reorganization of the Ethereum Classic blockchain during August and shifted part of the network’s security response from software engineering toward legal and regulatory pressure.

The organization said it was already working with authorities in relevant jurisdictions and would consider legal action against parties that conducted or facilitated malicious attacks. Those statements documented ETC Labs’ position and intended response. They did not establish that a regulator had opened a case, that a court had found wrongdoing, or that any hash-rental service had violated a specific law.

A third deep rewrite

Mining-pool operator Bitfly reported on August 29 that Ethereum Classic had undergone a reorganization exceeding 7,000 blocks, which it described as approximately two days of mining. In a proof-of-work blockchain, nodes generally accept the valid chain carrying the greatest accumulated work. An attacker controlling enough hash power can privately build an alternative history and release it after it overtakes the public chain, displacing blocks that participants had treated as confirmed.

A reorganization is not by itself proof of a successful theft. It can, however, enable a double spend if an attacker transfers coins to a service on the displaced history, withdraws something of value, then publishes a stronger chain in which the original transfer did not occur. The reviewed event-day records did not quantify losses from the late-August reorganization, so this reconstruction assigns no dollar amount to it.

The episode followed two earlier August attacks. Coinbase’s August 21 technical review placed the first at 10:57 p.m. Pacific time on July 31 and estimated about 800,000 ETC, then worth about $5.8 million, was double-spent. It placed the second at 8:15 p.m. Pacific time on August 5 and estimated roughly 460,000 ETC, then worth about $3.2 million, was double-spent. Coinbase said it was not a target and lost no funds. Those are Coinbase’s incident estimates for the earlier events, not measurements of the August 29 reorganization.

ETC Labs targeted the rental market

ETC Labs alleged that hash power bought through NiceHash had enabled earlier attacks. It argued that hash-rental services should face greater know-your-customer, anti-money-laundering and crypto-address-screening expectations, comparable in spirit to controls used by many digital-asset exchanges.

That was an advocacy claim by a network development organization, not an event-day regulatory finding against NiceHash. The August 31 statement did not identify a case number, participating agency, jurisdiction, requested rule, evidentiary standard or implementation timetable. Its assertion that rental markets could facilitate laundering also did not prove that every renter, rental transaction or platform was illicit.

The policy argument nevertheless mattered beyond Ethereum Classic. Rentable computing power made proof-of-work security partly dependent on an external marketplace. For a minority chain sharing a mining algorithm with a much larger network, temporary control could be economically accessible without an attacker buying and maintaining dedicated hardware. ETC Labs was effectively asking whether a service selling that capacity should bear duties when customers used it to rewrite a public ledger.

Engineering remained the immediate defense

Regulatory engagement could not repair consensus rules or protect a deposit in real time. ETC Labs’ August 19 security plan therefore proposed defensive mining, network monitoring, exchange coordination, higher confirmation requirements and a “Permapoint” finality system as near-term measures. Longer-term options included resistance to deep reorganizations, checkpointing and a possible change of proof-of-work algorithm, all subject to development and community agreement.

For exchanges, more confirmations reduced the chance of crediting a deposit that a later chain could erase, but increased settlement delays. For the protocol, checkpointing or subjective penalties could make deep reorganizations harder while changing assumptions about how nodes select history. None of those proposals had become a completed mainnet remedy on August 31.

The defensible event-day conclusion was narrow: ETC Labs escalated its response into a call for legal and regulatory scrutiny after repeated chain attacks exposed the economic security limits of a low-hash-rate proof-of-work network. Whether authorities would act, whether NiceHash bore responsibility, and which technical defense the community would adopt remained unresolved.