I have confirmation that we have one hour on March 7th at ETHCC to discuss this. It is on the ETHCC schedule under my name for 16:00 in Robert Faure.
My goal for it is to have a space where people can come and share the questions they have, and either get pointed to resources – like EthHub or the roadmap on the wiki – or capture those questions so that we can have discussions and find answers to them.
The guiding question is “What is the ETH1x Roadmap?”. Necessarily, this connects into planning for ETH2, and I definitely think there are a lot of ETH1 to ETH2 questions that are still open.
@lrettig said previously that he would volunteer to facilitate. I believe that a fishbowl format as we did for the ETH2 session at Council of Prague would be good to run this.
For now, I’m asking for your help in:
gathering resources – do you have good ETH1x materials to share like @AlexeyAkhunov’s state rent writings and presentations?
gathering questions – what questions do you have? Post them as a comment, and people can “heart” them if they have the same question.
@AlexeyAkhunov will sadly be unable to join in person but maybe we could get him to join virtually? It would be good to list questions here ahead of time so that Alexey and I can discuss them and make sure we’re prepared to answer them!
I have started working on some potentially pivotal changes in State Fees (rent) proposals - need to do some data analysis on the stateless client. Will try to get something up before that AMA
This (incorrect) roadmap is why we need to be more realistic and clear about ETH1x and ETH2 timelines. The more these “fast” dates float around, the more disappointment the realistic timelines will bring.
Timelines. ETH2 still has unknown components. And there is nothing that dapp developers or users can interact with until all of Phase 2. So how do we balance the realism of timing, with continued usage and adoption of ETH1?
pulling from Danny Ryan’s interview from Zero Knowledge on what happens to ETH 1 potentially moving to Eth 2.0 as a unique shard or otherwise:
Here is a rough transcript of his comments:
Whether ETH 1.x becomes a shard is really a community question, a research question. Though there are some technical challenges depending on the option.
Option 1: Roll ETH 1.0 into 2.0 once it reached an acceptable stability. (but how?)
Option 1A: 1.x as exceptional shard construction — however, separate rules from other shards and a legacy code base is really bad combination. Also wouldn’t be compatible with forecasted need for state fees.
Option 1B (favored by danny): write EVM interpreter in WASM. deploy as contract on ETH2.0— fork state root into contract and ether balances, then users can interact with 1.0 state by providing “merkel witnesses.” The community could then deprecate maintenance for ETH 1.0 but still interact with the historic state. Stateless nature means there wouldn’t be any issues with state fees.
Option 2: allow legacy chain to operate in perpetuity. At this point there is potential to use ETH 2.0 to finalise 1.0, allowing mining rewards to decrease further.
Option 3: Have mining rewards be a function of how much ETH is left on ETH 1.0
Generally, he thinks there are “promises” that need to be upheld, like an Augur market related to Mars that expires in many years.
Option 1 is an upgrade / migration, and pretty much requires coordination from existing users.
Option 1B seems most likely, and roughly what our EVM evolution work is planning for – that we HAVE to think about forward compatibility, make a plan for migration, and ideally evolve ETH1x so the migration is easier.
I’m not clear on the “wouldn’t be any issues with state fees” comment – because ETH2 shards have the same issue currently, and are likely to adopt similar state fees and/or need to solve it in some way.
