ethereum/pm

Ethereum Core Devs Meeting 91

timbeiko opened this issue ยท 8 comments

Ethereum Core Devs Meeting 91 Agenda

Agenda

  1. EIP Discussions
    • EIP-1559 Updates
    • Account Abstraction Updates
    • EIP-2046 Benchmarks
    • EIP-2718 Further Thoughts
    • EIP-2711 Introduction
  2. Network Health
    • ACD 90 (#189) Conversation Cont'd
    • Client Implementation Deep Dives
  3. Review previous decisions made and action items (if notes available)

Next call: July 24, 2020 14:00 UTC

Can I help to develop Ethereum somehow? I'm frontend vue/angular/react.

Potential questions to structure the discussion on specific implementations (Deep Dive):

  1. How does your team communicate with the users of your software? Do you know what at the most important things they care about?
  2. How does your team decide on priorities (what needs to be done next)?
  3. Do you rely on external (outside of your team) contributors or is most of the work done inside the team?
  4. What is the biggest recent (or ongoing) change you have been working on? Why did you decide to do it? What did you learn while doing it?

I'm hoping to facilitate some part of this conversation if people are open to it. I was not on ACD call 90 but after listening to it in its entirety it seemed to get bogged down focusing on solutions without first giving the problem space adequate exploration. I'm hoping that we can achieve the following.

  • loose understanding of the "client diversity problem".
    • What are the areas that have problems?
  • general consensus on what things specifically need to be fixed?
    • are people already actively working any of them?
    • are there problems that nobody is focused on (and which we think someone should). Why isn't anyone working on these thing?
  • general consensus on how we move forward
    • what are we in control of fixing, what do we have agency over?
    • how can we support this work?
    • how can we collaborate more efficiently?

I have no shortage of opinions about this subject. I'd encourage reading this if you are interested in my thoughts on the subject.

It would be great to hear any further thoughts on EIP-2718 that was discussed last week. Additionally, if there are a few minutes to spare I would like to briefly introduce EIP-2711: a new general tx format that is built on EIP-2718.

State tests were added for EIP 2537 in this PR

Quick announcement: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1057.md will be ready for review on this call two weeks hence, want to reach consensus on status two weeks after that. Current proposal is as follows.

Simple Summary

A new Proof-of-Work algorithm to replace Ethash that utilizes almost all parts of commodity GPUs.

We Do Not recommend that this Proposal be deployed at this time. Rather it is being offered in the spirit of Ben DiFrancesco's compromise which for our purposes we state simply as,

  • This Proposal is not being proposed for deployment in any planned hardfork.
  • This Proposal should be fully implemented and tested across major clients.
  • Clients implementing this Proposal should be deployed and maintained on a testnet.

This leaves open the possibility and threat of future deployment.

As mentioned on the call, we (the Quilt team) have put together an Account Abstraction Playground, which you can find here.

It bundles our MVP account abstraction implementation in geth with a forked version of solidity with basic AA support and some example contracts, as well as a step-by-step tutorial for getting started. I would recommend to anyone interested to take a look - playing around with AA is really quite interesting.

And to reiterate: This playground is not intended to address the valid questions around AA feasibility. We are still investigating these and will have a dedicated writeup once that's done.

Closed in favor of #195