Skip to content

network-spec: relax requirement after MsgIntersectFound #5187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 26, 2025
Merged

network-spec: relax requirement after MsgIntersectFound #5187

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7992b94
network-spec: fix typo
amesgen Aug 18, 2025
be3a60b
network-spec: relax requirement after `MsgIntersectFound`
amesgen Aug 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/network-spec/miniprotocols.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -876,9 +876,10 @@ \subsection{State Machine}
The consumer can decide whether to send more points.
The message also tells the consumer about the $tip$ of the producer.
Whenever the server replies with \MsgIntersectFound{}, the client can
expect the next update (i.e. a replay to \MsgRequestNext{}) to be
\MsgRollBackward{} to the specified $point_{intersect}$ (which makes
handling state updates on the client side easier).
expect the next update (i.e. a reply to \MsgRequestNext{}) to be
\MsgRollBackward{}, either to the specified $point_{intersect}$ or an earlier
point if the producer switched to a different fork in the meantime.
This makes handling state updates on the client side easier.
\item [\MsgIntersectNotFound{} {\boldmath $(tip)$}]
Reply to the consumer that no intersection was found: none of the
points the consumer supplied are on the producer chain.
Expand Down
Loading