From 36530fc7c66b0193aaa6e268c08098b742031117 Mon Sep 17 00:00:00 2001 From: Greg Fitzgerald Date: Wed, 5 Dec 2018 15:41:32 -0700 Subject: [PATCH] Fix link --- rfcs/0004-leader-rotation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/0004-leader-rotation.md b/rfcs/0004-leader-rotation.md index 3b3eff2c8a..bc0890d2ee 100644 --- a/rfcs/0004-leader-rotation.md +++ b/rfcs/0004-leader-rotation.md @@ -20,7 +20,7 @@ The seed that is selected is predictable but unbiasable. There is no grinding a Leader's transmit for a count of `T` PoH ticks. When `T` is reached all the validators should switch to the next scheduled leader. Leaders that transmit out of order can be ignored. -All `T` ticks must be observed from the current leader for that part of PoH to be accepted by the network. If `T` ticks (and any intervening transactions) are not observed, the network optimistically fills in the `T` ticks, and continues with PoH from the next leader. See [fork generation](rfcs/0002-fork-generation.md). +All `T` ticks must be observed from the current leader for that part of PoH to be accepted by the network. If `T` ticks (and any intervening transactions) are not observed, the network optimistically fills in the `T` ticks, and continues with PoH from the next leader. See [fork generation](0002-fork-generation.md). ## Network Variables