Eth2.0 Implementers Call 15 Agenda

[djrtwo]

Eth2.0 Implementers Call 15 Agenda

Meeting Date/Time: Thursday 2019/3/28 at 14:00 GMT

Meeting Duration 1.5 hours

YouTube Live Stream Link

Agenda

1. Testing Updates
2. Client Updates
3. Research Updates
4. Network Updates
5. SSZ/SOS update from piper
   • Update SSZ spec to use SOS style offset based layout. consensus-specs#787
6. Testnets progress, roadmap, PM
7. Spec discussion
8. Open Discussion/Closing Remarks

[Mikerah]

I would like to discuss ETH2.0 project management for a multiclient testnet. I have enlisted the help of the Ethereum Cat Herders (@poojaranjan, @CPSTL, @dangerousfood, @decanus, Helena Flack, @mariapaulafn).

This will require coordination among all the ETH2.0 team and I think it makes sense to have processes in place to make sure this is done on time and clearly communicated to the community.

[jrhea]

Can we discuss the status of the Phase 0 Networking Specification? Several of us working on the Hobbits wire protocol implementation have some comments/suggested changes. It is dysfunctional to leave this Phase 0 Network Specification PR open forever. There are a dozen unanswered comments and we can't propose PR's to a PR that never closes. We need to stop trying to make it perfect on the first try and start iterating.

[djrtwo]

I would like to discuss ETH2.0 project management for a multiclient testnet.

I am of the opinion that there are no two teams that are ready to target interoperability with another client and that it will be a waste of time and resources to do so before (1) the clients in question have a long standing single testnet, (2) the clients in question target the same exact release of the spec, and (3) the clients in question pass all consensus test vectors related the release.

I'm also of the mind that these early interop experiments should not be a large organized effort and should instead be teams one on one working with each other. Only once we have ironed out some more isolated 1 on 1 client testnets should we begin to target a general purpose, long-standing, multi-client testnet.

Edit: I'm not against organizing our efforts, but I don't want to jump the gun and waste resources. My opinion is that anytime in the next month is likely jumping the gun. Single client test nets should be actively worked on, communicated to the community, and celebrated as we continue to refine and iron things out with the spec, testing, and network protocol