You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: simulation/docs/network-spec/miniprotocols.tex
+13-7Lines changed: 13 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -255,7 +255,6 @@ \subsection{Producer and Consumer Implementation}
255
255
It replies with not more than the requested number of ids (possibly with an empty list).
256
256
A blocking request on the other hand, waits until at least one datum is available.
257
257
258
-
259
258
It must however observe several constraints that are necessary for a
260
259
memory efficient implementation of the provider.
261
260
@@ -286,6 +285,16 @@ \subsection{Producer and Consumer Implementation}
286
285
intend on requesting any of the available datums.
287
286
288
287
288
+
\paragraph{Equivocation handling} IB-relay, EB-relay, and Vote-relay must guard against the possibility of equivocations, i.e. the reuse of a generation opportunity for multiple different blocks.
289
+
The \emph{message identifier} of an header is the pair of its
290
+
generating node id and the slot it was generated for\footnote{for IBs/EBs also its subslot, in
291
+
case generation frequency is greater than $1/\text{slot}$}. Two headers
292
+
with the same message identifier constitute a \emph{proof of
293
+
equivocation}, and the first header received with a given message
294
+
identifier is the \emph{preferred header}. For headers with the same
295
+
message identifier, only the first two should be relayed, furthermore
296
+
only the body of the preferred header should be fetched.
0 commit comments