Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ethereum Core Devs Meeting 74 Agenda #134

Closed
timbeiko opened this issue Oct 29, 2019 · 5 comments
Closed

Ethereum Core Devs Meeting 74 Agenda #134

timbeiko opened this issue Oct 29, 2019 · 5 comments

Comments

@timbeiko
Copy link
Collaborator

timbeiko commented Oct 29, 2019

Ethereum Core Devs Meeting 74 Agenda

Agenda

  1. Istanbul updates, if any
  2. Berlin
    • Ice Age
    • Tentatively Accepted EIPs
      • EIP-663: Unlimited SWAP and DUP instructions
      • EIP-1380: Reduced gas cost for call to self
      • EIP-1702: Generalized account versioning scheme
      • EIP-1962: EC arithmetic and pairings with runtime definitions
        replaces EIP-1829
      • EIP-1985: Sane limits for certain EVM parameters
      • EIP-2045: Particle gas costs for EVM opcodes
      • EIP-2046: Reduced gas cost for static calls made to precompiles
      • EIP-1057: ProgPoW, a Programmatic Proof-of-Work
    • Process & scheduling discussions
  3. Testing updates
  4. Review previous decisions made and action items
    • Call 73 [Notes TBA]
  5. Client Updates (only if they are posted in the comments below)
    a) Geth
    b) Parity Ethereum
    c) Aleth/eth
    d) Trinity/PyEVM
    e) EthereumJS
    f) EthereumJ/Harmony
    g) Besu
    h) Turbo Geth
    i) Nimbus
    m) Nethermind
  6. Research Updates (only if they are posted in the comments below)
@pizzarob
Copy link

Is it possible to discuss ethereum/EIPs#2310 during this next meeting?

@sorpaas
Copy link
Contributor

sorpaas commented Oct 29, 2019

From Berlin hard fork we'll be using an EIP-centric process, and each proposed EIP now must have a champion. I have no plan to become "champion" of any EIPs because that will mean I need to take a political stance. As a result, I'll be pulling EIP-1702 (account versioning) out of Berlin, unless someone else volunteers to champion it. ethereum/EIPs#2326

Regarding the specification -- I think we currently have a pretty good backward compatibility solution (via EIP-1702 account versioning, plus forward-compatible "versionless" EVM), which addresses most of the concerns since last discussion (maintenance cost, sustainability). If you want to know more, I'm pointing you to my devcon talk: https://twitter.com/sorpaas/status/1188611187413585920

@Souptacular
Copy link
Contributor

Hey @pizza-r0b! ERC standards are not generally discussed in core developer meetings because core developer meetings deal with low-level protocol specifications.

@axic
Copy link
Member

axic commented Nov 5, 2019

@timbeiko
Copy link
Collaborator Author

Closed in favor of #138

timbeiko added a commit that referenced this issue Mar 29, 2022
Ethereum Core Devs Meeting #134 and update readme file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants