From ffc82c027e3679b0cae6553669b4fc3f0d429099 Mon Sep 17 00:00:00 2001 From: Greg Fitzgerald Date: Mon, 10 Dec 2018 09:53:56 -0700 Subject: [PATCH] Fix markdown rendering --- rfcs/0002-fork-generation.md | 1 + 1 file changed, 1 insertion(+) diff --git a/rfcs/0002-fork-generation.md b/rfcs/0002-fork-generation.md index a4bb50088..3bb7643b5 100644 --- a/rfcs/0002-fork-generation.md +++ b/rfcs/0002-fork-generation.md @@ -54,6 +54,7 @@ The diagram below represents a validator's view of the PoH stream with possible | +----+ | | | | | | | | vote(E4) v | L5 | xx xx xx E5 xx xx xx xx +----+ hang on to E4 and E5 for more... +``` Note that an `E` appearing on 2 forks at the same slot is a slashable condition, so a validator observing `E3` and `E3'` can slash L3 and safely choose `x` for that slot. Once a validator commits to a forks, other forks can be discarded below that tick count. For any slot, validators need only consider a single "has entries" chain or a "ticks only" chain to be proposed by a leader. But multiple virtual entries may overlap as they link back to the a previous slot.