"eth" | "ethereum" | "foundation" | "mainnet" => SpecType::Foundation, "etc" | "classic" => SpecType::Classic,
There is a great talk by Charles Hoskinson at ETC Summit 2017 which I only saw for the first time around two weeks ago.
In it he talks about "The Two Ethereums" always existing, but the irreconcilable difference between those visions only becoming apparent at the time of the DAO fork.
Those two visions were "A Better Bitcoin" and "World Computer". We call those visions ETC and ETH2 these days. And I guess ETH1 is "World Computer Prototype"?
The "right answer" on "what to do" at the time of the DAO fork was different for these two visions. Hence the split.
The beautiful truth in this insight is that there is no conflict whatsoever between these two visions - they are entirely complimentary. We FINALLY seem to be getting to the point where we can respect that duality, and we can collaborate on the huge technical commonality, while maintaining the differing philosophies.
So that is pretty much the scope of ETC.
It is a much more tractable problem.
"So what is the scaling plan for ETC?"
L2. State Channels already work on ETH2 (Fate Channels + Connext already in production).
Fate Channels don't need CREATE2 so will work today on ETC as well.
Connext will work on ETC when we get Constantinople opcodes at Agharta in Jan 2020:
The plan for scaling L1 on ETC is not to scale L1.
Or at least to only do that in a sustainable "Moore's law" style manner.
Only to the degree which the current tech stack can support.
Security always comes first for ETC.
"Better Bitcoin", not "World Computer"
Hope that gives everyone some more insight into the thinking.
@/all Core dev meeting in 10 min.
Zoom Link: https://zoom.us/j/121989443
Regarding the discussion in the meeting on tooling support for EIP-1707 code prefix vs 44-VERTXN account versioning extension. Thanks to MrChico for spotting this -- the concern on 44-VERTXN's ecosystem tooling support can be wholly addressed just by making the
version field optional with default value
This I believe, from all information I have in hand, means that 44-VERTXN is nearly superior in all aspects compared with EIP-1707 code prefix.