I would like to launch a working group on Eth1 implementation architecture.
It has been recognised that a lot of Eth1 implementations tend to become more monolithic over time, with optimisations cutting across various components. This makes it harder to study the architecture of such implementation (because it usually means studying a lot of code), and limits the extent to which implementers can specialise in specific components.
The work that this working group would be doing at first would mostly be modelling and technical writing. would love to see modelling happening in a “guided discovery” mode, and I can be one of the guides. Other guides could be people who know details of a specific implementation but never had a chance to generalise and deepen their knowledge.
Outputs will be models of various things like p2p peers, header chains, block chains, state, evm, things inbetween EVM and state etc. And hopefully these models can be used to construct a reference architecture with some form of spec, which will also define common terminology. To recap, I see 4 types of output:
- models of entities for the architecture
- reference architecture, which is collection of entities and data flow requirements/interfaces between them
- terminology for the entities
- specification describing the reference architecture