Ethereum Core Devs Meeting 74 Agenda
timbeiko opened this issue · 5 comments
Ethereum Core Devs Meeting 74 Agenda
- Meeting Date/Time: Friday 1 November 2019, 14:00 UTC
- Meeting Duration 1.5 hours
- YouTube Live Stream
- Istanbul Meta EIP
- Berlin Meta EIP
Agenda
- Istanbul updates, if any
- 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
- Testing updates
- Review previous decisions made and action items
- Call 73 [Notes TBA]
- 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 - Research Updates (only if they are posted in the comments below)
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: