Update cardano-blueprint #582
Description
Why
Following the impact analysis and the technical design document, both of which are node-level specifications and specific to the Haskell cardano-node, we can contribute implementation-independent parts of the necessary changes to other node implementors via the cardano-blueprint project. This will be a first step to support node diversity even on new developments like Leios.
What
- Leios-specific changes must be clearly marked as "future" and not currently active changes
- Ideally a reader can turn them on or off
- Add new N2N mini-protocols to network chapter of cardano-blueprint
- Update block production and chain validity sections on the cardano-blueprint
- Add ledger/crypto (voting + certs) changes to the cardano-blueprint
How
- Establish a means to mark Leios changes
- Best case: (code) fences in markdown which render in different color on the PDF and have a UI element on the web rendering; For example like the ZCash specification
- Worst case: collapsible sections
Example
Leios changes would be here (not the best solution)- Submit pull requests to https://github.com/cardano-scaling/cardano-blueprint