This thread is a proposal to create a meta-working-group for Ethereum 1x, ETH 1x, or “1x”-related discussions and coordination.
The initial discussions started in Prague around Devcon4, the following two previous threads pretty much sum up the what has been proposed so far:
- Kicking off the debate Thread to begin discussing "Ethereum 1.0" proposals
- Not suggesting a roadmap yet Ethereum 1 dot X: a half-baked roadmap for mainnet improvements
To summarise, we see the strong need to bridging the gap between the “legacy” Ethereum (1.0) and the “future” Ethereum (2.0, aka Serenity) with something unspecific we call 1x (a.k.a 1.x).
Participants of the various discussions and working groups agreed to have a joint call on Nov-30, 2018: https://github.com/ethereum/pm/issues/65
The current 1x working groups are:
- State Rent Ethereum State rent for Eth 1.x pre-EIP document
- eWasm Ewasm working group proposal for Eth 1.x
- eWasm (duplicate) Ethereum 1.x - Ewasm Working Group proposal
- Simulation of changes/data to inform motivation (Shahan from Pantheon to lead)
- Reducing storage via archiving logs and blocks (Peter from go-ethereum to lead)
- your proposal here …
However, there are some open questions:
- How to transition from a rent-less system to a state-rent system?
- How to deal with “legacy” contracts?
- Is it sufficient to introduce concepts like rent in mid-2019 or shall we think further?
- How to transition from EVM 1.0 to an EVM 1.5 or eWasm environment?
- Does it make sense to talk about block pruning?
- Does it make sense to reset the state at some point?
- Is it worth to consider 1x to be launched as a new, clean, bridged mainnet?
I don’t seek immediate answers to these questions, especially not technical solutions, but would instead encourage people to contribute to a working group that tries to keep an eye on the meta-issues related to 1x, to potentially map out different scenarios for a transition, and finally to propose realistic roadmaps.