From e53623f005bae0bd9994ae710656aacb0300e864 Mon Sep 17 00:00:00 2001 From: nate Date: Tue, 7 Nov 2023 11:51:07 -0800 Subject: [PATCH] Remove trailing whitespace. --- src/diagrams/zcash-tech-tree-tfl-steps.dot | 2 +- src/introduction/a-path-to-pos-zcash.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/diagrams/zcash-tech-tree-tfl-steps.dot b/src/diagrams/zcash-tech-tree-tfl-steps.dot index 68b1cec..c9a51d8 100644 --- a/src/diagrams/zcash-tech-tree-tfl-steps.dot +++ b/src/diagrams/zcash-tech-tree-tfl-steps.dot @@ -22,7 +22,7 @@ digraph ZcashTechTreeGeneric { e [ label = "Feature E"] e -> pos2 e -> d - + pos1 [ label = "TFL v1"] pos1 -> nu5 diff --git a/src/introduction/a-path-to-pos-zcash.md b/src/introduction/a-path-to-pos-zcash.md index 9bf2298..2c24fb6 100644 --- a/src/introduction/a-path-to-pos-zcash.md +++ b/src/introduction/a-path-to-pos-zcash.md @@ -23,7 +23,7 @@ After this transition to pure PoS, there are likely to be future improvements to Our primary motivation for proposing (at least) two steps is to minimize disruption to usability, safety, security, and the ecosystem during each step. -This book primarily focuses this first step: the transition to [PoW+TFL](../terminology.md#definition-pow-tfl). To understand the specific goals for that, see [Design Goals](../overview/design-goals.md). +This book primarily focuses this first step: the transition to [PoW+TFL](../terminology.md#definition-pow-tfl). To understand the specific goals for that, see [Design Goals](../overview/design-goals.md). With this approach, the Zcash Tech Tree with the [TFL](../terminology.md#definition-tfl) approach might look something like this: @@ -33,7 +33,7 @@ With this approach, the Zcash Tech Tree with the [TFL](../terminology.md#definit ## Why Two Steps? -One question we've gotten in proposing this approach is why take a two-step process with an intermediate [hybrid consensus](../terminology.md#definition-hybrid-consensus) protocol, rather than a single transition directly to a [PoS](../terminology.md#definition-pos) protocol? +One question we've gotten in proposing this approach is why take a two-step process with an intermediate [hybrid consensus](../terminology.md#definition-hybrid-consensus) protocol, rather than a single transition directly to a [PoS](../terminology.md#definition-pos) protocol? Here's how we think about those trade-offs: