Ethereum Core Devs Meeting 62 Agenda
lrettig opened this issue · 12 comments
Ethereum Core Devs Meeting 62 Agenda
- Meeting Date/Time: Friday 24 May 2019 at 14:00 UTC
- Meeting Duration 1.5 hours
- YouTube Live Stream
Agenda
- Review previous decisions made and action items
- Roadmap
- EIPs
a) Refer to Roadmap link for list
b) EIP-2045: Fractional gas costs, and the EVM benchmarks referenced within (cdetrio) - Working Group Updates
- Testing Updates
- 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) Pantheon
h) Turbo Geth
i) Nimbus
j) web3j
k) Mana/Exthereum
l) Mantis
m) Nethermind - EWASM & Research Updates (only if they are posted in the comments below)
Re: ACTION 58.1: Cat Herders to look at updating EIP1. Status: Work in Progress, this is the relevant PR: ethereum/EIPs#1991
Could people please leave comments/feedback prior to the next AllCoreDevs, if they have any. If not, I would suggest that this gets merged & the action item gets marked as done.
For client updates PegaSys shipped the 1.1.1 release of Pantheon. The biggest feature was integration of the GraphQL endpoint as described in EIP-1767.
I'd like to discuss EIP-2045: Fractional gas costs, and the EVM benchmarks referenced within.
I would like to discuss what EIPs are "getting on the list" for Istanbul. The discussion in the all-core-devs chat was to move the deadline to this call.
This is our first time through the EIP driven network upgrade process, so I don’t think any of these rules are hard and fast but are taken more of a measure of what EIPs are viable for this specific network upgrade. The fact there is a document that can be pointed to and a person willing to attend calls and advocate on FEM I think are the two strongest indicators, aside from the next checkpoint which is actual implementation in clients.
This is a good summary from FEM but, I don't think there is consensus on this yet.
There is currently a list of 35. 24 have been merged as Draft.
https://docs.google.com/spreadsheets/d/1Mgo7mJ6b6wimUwafsMo1l-b44uec28E_Hq8EQ7YdeEM/edit#gid=0
)
^ Current status of the EIPs on that list regarding checkpoint 1. Reaching 4 means it has been merged as draft.
Which of these make it past checkpoint 1 (are considered for Istanbul)? How do we decide?
Questions
-
Is there a need to actively reduce this list before the next deadline, or can we let the deadline reduce itself as different EIPs are worked on themselves?
-
Is there a person/persons going to manage this process?
-
What does the process for this look like? (As a best guess)
-
What are concerns of a list this large? Is it due to the coordination involved?
Two EIPS I would like to bring up specifically in the context of Istanbul.
- ethereum/EIPS/#2024
- ethereum/EIPS/#2025
Client update: we released a new alpha of Trinity earlier this week: https://github.com/ethereum/trinity/releases/tag/v0.1.0-alpha.24
improvements to peer discovery & communication, sync reliability, performance, and custom networks.
Parity Ethereum client update: Parity-Ethereum 2.5.1-beta is a bugfix release that improves performance and stability.
Among others, it enables the Petersburg hardfork on Rinkeby and POA-Core Network, as well as the Kovan Network community hardfork.
The "Roadmap" list above states:
The list of EIPs in 1679 are the canonical status of EIPs
However, the list of EIPs in the Roadmap document is out of sync with EIP-1679. Would it make sense changing the "Roadmap" link in the agenda above to EIP-1679?
@axic Yes
Link here https://eips.ethereum.org/EIPS/eip-1679
EIPS status update: 5/24/19
Processed: 11-34
- y* - 3
- tbd - 7
- n* - 1
Not sure how official this is, chart above is from the following Istanbul EIP Readiness Checklist, just dropping here for context.
(@MadeofTin I assume I can publish here since you posted this in the public Gitter channels)