Leios design: Write interactions with other protocols sections #594
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
12 tasks
ch1bo
force-pushed
the
ch1bo/dependencies-interactions
branch
from
34981ad to
e1c1d19
Compare
ch1bo
commented
Oct 25, 2025
|
|
||
| The implementation of Ouroboros Leios represents a substantial evolution of the Cardano consensus protocol that must integrate carefully with existing infrastructure and emerging features. This section examines the critical dependencies that must be satisfied before Leios deployment, identifies synergies with parallel developments, and analyzes potential conflicts that require careful coordination. The analysis informs both the implementation timeline and architectural decisions throughout the development process. | ||
|
|
||
| ## On-disk storage of ledger state |
| - Leios vote production thread can be generalized for Peras votes | ||
| - Network multiplexer handles three priority levels: Peras > Praos > Leios | ||
| - Shared telemetry and monitoring infrastructure | ||
| ## Era and hard-fork coordination |
There was a problem hiding this comment.
@lehins @disassembler What is your take on upcoming eras and their schedule across hard-forks?
There was a problem hiding this comment.
I'm planning to update this section based on your comment yesterday @lehins: we should be targeting the next-up era (Dijkstra) even if we might need to move things into a further era later. Besides, if we get the serialization specified and implemented for Dijkstra, we can "feature flag" it behind a protocol version easily and enable Leios in an intra-era hard-fork.
There was a problem hiding this comment.
Addressed in f65a33c. Would you agree with that take?
| - Enables incremental complexity management | ||
| Therefore, we suggest to target the `Euler` era for Leios deployment, with the option to advance the timeline into `Dijkstra` if the development schedule permits. This is preferrable because merging features into an era is expected to be easier than splitting an era into two during development. Consequently, targeting `Euler` also provides flexibility in addressing any unexpected technical challenges that emerge during implementation while ensuring that Leios development does not become a blocking dependency for other planned protocol upgrades. | ||
|
|
||
| ## Interactions with Genesis |
There was a problem hiding this comment.
I'm not really a Genesis expert and would love to have this reviewed by someone in the know!
@nfrisby Would you be a good person to ask or you know who would be one?
12 tasks
amesgen
reviewed
Oct 27, 2025
ch1bo
changed the title
ch1bo
force-pushed
the
ch1bo/dependencies-interactions
branch
2 times, most recently
from
0f7df84 to
5e93857
Compare
ch1bo
force-pushed
the
ch1bo/implementation-plan
branch
from
d345b94 to
659364c
Compare
ch1bo
force-pushed
the
ch1bo/dependencies-interactions
branch
from
5e93857 to
c536295
Compare
amesgen
approved these changes
Oct 29, 2025
jpraynaud
approved these changes
Oct 29, 2025
ch1bo
force-pushed
the
ch1bo/dependencies-interactions
branch
from
a54934b to
e5ac5c7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a chapter on key dependencies and interactions with notably other Cardano protocol features to the Leios technical design and implementation plan as part of #542
In particular this covers on-disk storage, era/hard-fork coordination, Peras, Genesis, and Mithril.
I'm not 100% in the know on all statements contained and will tag a few people for focused review.
Rendered