ProgPoW Code Advanced as Ethereum’s ASIC Debate Intensified

A working Go implementation of ProgPoW was updated on September 22, 2018 as Ethereum miners and developers intensified a public argument over whether the network should change its proof-of-work algorithm to blunt the advantage of specialized mining hardware.

The code update did not change Ethereum’s consensus rules. It mattered because it placed an executable artifact beside a governance dispute that had moved beyond theory: GPU miners were warning about application-specific integrated circuits, while client developers were weighing decentralization claims against the risk of rushing a consensus-breaking change.

Code, proposal and an unsettled network

GitHub records developer Alexey Akhunov’s `progpow.go` gist as last active on September 22. The file contained functions for “light” and “full” ProgPoW hashing and imported cryptographic code from Go Ethereum. Its existence demonstrated implementation work, not review, client integration or readiness for mainnet deployment.

ProgPoW had already been proposed as EIP-1057 on May 2, 2018. The proposal’s stated aim was to replace Ethash with a workload using more of the capabilities found in commodity graphics processors. Its authors argued that matching the workload more closely to GPUs would narrow the efficiency gap available to custom ASICs.

That was a design objective, not an independently established result. Specialized hardware could still be built, and the event-day record did not quantify how much advantage any production ASIC would retain under ProgPoW.

Developers resisted an immediate fork

Contemporaneous reporting on September 22 documented calls by some GPU miners for a “strike” and competing caution from Ethereum developers. The important institutional point was not that either faction had won, but that maintainers were discussing a possible mining-algorithm fork while refusing to fold it into Constantinople, the next planned network upgrade.

Ethereum Foundation security officer Martin Holst Swende argued that implementation alone was insufficient and that a safe switch required testing. He favored considering a dedicated proof-of-work change after Constantinople rather than adding ProgPoW to that upgrade. Client developer Afri Schoedon likewise said Constantinople’s contents were effectively final after months of work. Developer Nick Johnson supported ProgPoW’s goals but also agreed that Constantinople was already settled.

Those positions left a path for later evaluation without creating an activation schedule on September 22. No block number, release version or binding adoption decision was announced.

Why the hardware question mattered

Proof-of-work hardware determined who could compete to produce Ethereum blocks and receive rewards. GPU advocates argued that widely available equipment lowered barriers to entry and reduced dependence on a small group of ASIC manufacturers. Opponents of a hurried change could point to a different decentralization risk: a contentious algorithm switch might split miners, clients and applications across incompatible chains.

The debate therefore joined economics to protocol governance. A technically functional hash implementation could not settle whether the expected distribution benefits justified deployment risk. Nor could comments from miners or individual developers substitute for compatible client code, coordinated releases, testing and voluntary adoption by node operators.

Ether’s market did not provide a clean verdict. CoinMarketCap’s September 22 historical snapshot recorded ETH at $240.48, down 2.72% over its 24-hour window, with reported volume of $1.92 billion and quoted capitalization of $24.56 billion. Kraken’s venue-specific daily report recorded ETH at $242.20, also down 2.71%, on $45.4 million of exchange volume. The similar percentage changes came from different market universes and cutoff methods; neither dataset establishes that ProgPoW discussion caused the move.

What September 22 established

The defensible event-day conclusion is narrow. ProgPoW had an active proposal, working experimental code updated on September 22 and visible support among parts of Ethereum’s mining and developer communities. It was not an approved Ethereum upgrade, and it was not part of Constantinople.

No reliable September 22 measurement in the reviewed sources established Ethereum’s ASIC share, the number of miners prepared to strike or the performance of the Go implementation across production hardware. Those uncertainties are central, not incidental: the day captured an open-source network confronting how much evidence and coordination should be required before changing the machinery that secured it.