hardfork-planning: initial dijkstra scope - #54
Merged
Conversation
disassembler
force-pushed
the
sl/dijkstra-scope
branch
from
July 15, 2026 12:24
08096f1 to
498173c
Compare
disassembler
force-pushed
the
sl/dijkstra-scope
branch
from
July 16, 2026 13:53
498173c to
bbffb58
Compare
CarlosLopezDeLara
approved these changes
Jul 21, 2026
disassembler
force-pushed
the
sl/dijkstra-scope
branch
from
July 21, 2026 19:21
6f6a225 to
918eedc
Compare
nfrisby
reviewed
Jul 21, 2026
nfrisby
left a comment
nfrisby
left a comment
There was a problem hiding this comment.
This review assessed various wordings, without considering details of the timelines/durations---I'm not prepared to do that right now.
- Correct Peras: votes/certs exist outside the chain; block bodies optionally carry a cert (not headers); rename to codec extensions - Correct CIP-164 row: note block bodies can carry a Leios cert - Soften Full Leios paragraph: frame as research readiness rather than dead end, remove incorrect claim about new cryptography required - Fix RB announcement: header carries hash of EB, not the EB itself - N2N: new node-to-node protocols, not the existing ones - Remove IB references from testing table and activates list - Note Leios throughput parameters will be ramped gradually via governance
|
That new commit looks great; address my comments. (Which I for some reason cannot Resolve 🤷) |
Collaborator
Author
|
This may need to be revisited with IntersectMBO/cardano-ledger#5943 live now. For now I'm keeping it the same, but we can always merge changes later. |
ch1bo
reviewed
Jul 23, 2026
| |-------|-----------|-----|---------------------|--------------------| | ||
| | [Phase 1](#phase-1-dijkstra-hard-fork-protocol-version-12-october-2026) | New era (v12) | Dijkstra | October 2026 | Nested Transactions, block body extensions for Leios & Peras | | ||
| | [Phase 2](#phase-2-linear-leios-activation-intra-era-hard-fork-q1-2027) | Intra-era hard fork | Dijkstra | Q1 2027 | Ouroboros Linear Leios | | ||
| | [Phase 3](#phase-3-peras-activation-intra-era-hard-fork-q2-2027) | Intra-era hard fork | Dijkstra | Q2 2027 | Ouroboros Peras | |
There was a problem hiding this comment.
Is the ecosystem ready for a hard-fork every 3 months? PV11 took more than 6 months after code freeze and past hard-forks with comparable scope to these took even longer.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
No description provided.