-
Notifications
You must be signed in to change notification settings - Fork 166
Description
What content is missing?
The CL architecture page offers only a broad overview derived from the Honest Validator Guide (CL specs) and doesn’t adequately address how the node is structured or starts up. While each client has unique characteristics, many implementation details—such as service management and general system behavior—are shared across clients. Documenting these core similarities, highlighting relevant trade-offs, and clarifying which aspects are client-specific (and thus prone to rapid change) could greatly enrich the current material. At present, the architecture documentation does not fully capture the complexities of how clients are built. Improving it would be beneficial; although this point is based on the CL side, the same might also apply to the EL documentation.
Related content in the wiki
https://github.com/eth-protocol-fellows/protocol-studies/blob/main/docs/wiki/CL/cl-architecture.md
Other relevant resources
private WIP notes
-
ethereum by second : what happens in the node at each slot and partial slot
Really nice resource