Thread by @wsfoxley

I'll be live tweeting this morning's Ethereum AllCoreDevs call on ProgPoW, a controversial mining algo update which has made its way around the eth dev carousel a few times.

Read @BradyDale's recent explainer to catch up!
coindesk.com/ethereums-prog…

the first hour is on eth2.0 BLS signatures under EIP 1962. Will get to ProgPoW in about an hour.

Repping the pro-ProgPoW side is @OhGodAGirl and @BitsBeTrippin

Anti is repped by @koeppelmann and @mhluongo with @BenDiFrancesco proposing a middle ground

.@VitalikButerin is joining today's call, but its unlikely he weighs in on ProgPoW given his focus on eth2.0

Time for ProgPoW: 1) technical updates 2) community discussion and 3) next steps for the ethhash replacement

.@OhGodAGirl talking about ethhash's DAG overload and subsequent network hash rate dropping source:

https://twitter.com/TimBeiko/status/1235948236340412418

.@koeppelmann comes out first against ProgPoW, saying its not clear why ethereum should be against ASICs:
1) ASICs are a capital investment, like PoS
2) Does ProgPoW even achieve ASIC resistance?
3) Not aware of any project that wants it

.@mhluongo says ProgPoW is showing a breakdown in ethereum governance. Devs and others were surprised ProgPoW was still a topic.

Compares ProgPoW to bitcoin's 2016/17 community wars

As @BradyDale noted yesterday, lots of projects (#DeFi) are built on ethhash and would break under ProgPoW. Projects, not individuals, will decide which chain to operate on.

https://twitter.com/TimBeiko/status/1235954997659131910

https://twitter.com/TimBeiko/status/1235955634765467648

.@BitsBeTrippin says "the ability to participate" in mining is healthier for the community and eth2.0's vision. Hints that this call won't be a sufficient platform to solve the topic.

. @OhGodAGirl says mining is often a gateway for bringing people into the ethereum community. ASIC only can be a gateway for new users who typically join with GPUs first.

.@BenDiFrancesco discussing his compromise:

"I don't think the path forward is one group convincing the other...everyone wants to avoid a chain split [though]"

Calls for ProgPoW to be used as an insurance policy in case of an ASIC attack, but not as the new hashing function given its limited upside + distracts from eth2.0

**What an ASIC attack *is* is not well defined. Perhaps something to do with further mining consolidation around ASICs?

https://twitter.com/TimBeiko/status/1235959525095739392

.@koeppelmann asks where the concern that ASICs taking over the network will come from given the # of ASICs online is supposedly going to drop 40% in the next few months.

.@mhswende says this is a forward-looking issue

@koeppelmann says eth2.0 is the solution ProgPoW supporters are looking for

**Note: Eth1.x's PoW chain will live in Eth2.0 as a shard, meaning the PoW will continue to exist for a few months/yrs after eth2.0 launch

.@koeppelmann says a hard fork means convincing 20,000 people that a major change is needed. Resources are better spent on eth2.0

.@GuthL is worried the ethereum network will become dependent on the whim of ASIC manufacturers if the hashing algo slowly phases out GPU mining

.@ameensol
comes out swinging, calls ProgPoW "profit seekers" who can't be trusted

"anyone who thinks code chain is trivial is not taking this seriously"

either way, @ameensol supports @BenDiFrancesco's compromise -- lets do this when the network needs it, not based on profit

.@peter_szilagyi says putting the code behind the scenes until the network is ready could be dangerous. He supports one testnet with ProgPoW running in case the network does not it, however. As I understand it, this works with @BenDiFrancesco compromise.

some more from @GuthL 👇

https://twitter.com/GuthL/status/1235965394776723457

.@hudsonjameson says there is not a well-defined process for core devs next move --> where will the EIP go? Needs Core Dev support

@ameensol (not a core dev) volunteers to move on a decision. Can't tell who, but someone yelled at him 😅

The ProgPoW EIP won't move from its "accepted" status regardless of today's discussion (or the last 1.5 yrs). The community will keep discussing

.@JHancock (eth hard fork coordinator) confirms it will not go into hard fork schedule

Core Devs believes the community is against ProgPoW and the it needs more testing before going forward.

Tomaz Stanczack of @nethermindeth says they are not supporting as of now

Call ends on that note:
Watch the livestream again here: youtube.com/watch?v=kham8c…

Also great tweet thread here:

https://twitter.com/TimBeiko/status/1235924874973138944