Why

The CIP is a protocol-level specification of what the Leios protocol could be (and why it is a good idea). It only briefly touches on what the concrete changes on a Cardano node would be. While we want to also produce implementation-independent documentation, a node-level look at how Leios could be implemented is a key artifact to motivate and guide the next steps. Also, it will serve as a deliverable to Intersect.

What

Topics to cover:

• Summarize the CIP and its impact onto the node (further refined from Impact analysis document #546)
  • Concrete changes to node architecture, supported by a C4 component diagram?
• Identify/list key risks or assumptions to validate early
• Motivate a rough simulations -> prototype -> testnet plan
• What kind of prototype should we build?
• What experiments / tests should we conduct (on a testnet)?
• Synergies with Peras
• Interactions with Genesis (catching up node)
• Key generation, registration, rotation (in more detail)
• ...

How

• A markdown document on the leios github repository should be sufficient
• Render it into a PDF to follow suite with peras: https://tweag.github.io/cardano-peras/peras-design.pdf
• Scaffold a technical design document #581
• Create a C4 component diagram with the component changes
• Specify technical details for all individual changes (by component, by topic?)
• Write implementation plan section
• Write interactions with other protocols section
• ...