-
Notifications
You must be signed in to change notification settings - Fork 325
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
Comments
Is it possible to discuss ethereum/EIPs#2310 during this next meeting? |
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 |
Hey @pizza-r0b! ERC standards are not generally discussed in core developer meetings because core developer meetings deal with low-level protocol specifications. |
Merged the PRs to mark some of the Istanbul EIPs Final: |
Closed in favor of #138 |
Ethereum Core Devs Meeting #134 and update readme file
Ethereum Core Devs Meeting 74 Agenda
Agenda
replaces EIP-1829
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
The text was updated successfully, but these errors were encountered: