From 68ff25901ffa06efbac60234366006358a94d8a4 Mon Sep 17 00:00:00 2001 From: Jasmina Malicevic Date: Fri, 20 May 2022 15:42:28 +0200 Subject: [PATCH] Fixed links --- spec/blocksync/readme.md | 2 +- spec/blocksync/verification.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/spec/blocksync/readme.md b/spec/blocksync/readme.md index 144371b7b..a431119e3 100644 --- a/spec/blocksync/readme.md +++ b/spec/blocksync/readme.md @@ -56,6 +56,6 @@ This section describes the Blocksync reactor and its internals including: - [Peer to peer communication pattern](./communication.md) - [Block Verification](./verification.md) -More details on how to use the Blocksync reactor and configure it when running Tendermint can be found [here](./../docs/tendermint-core/block-sync/README.md). +More details on how to use the Blocksync reactor and configure it when running Tendermint can be found [here](./../../docs/tendermint-core/block-sync/README.md). diff --git a/spec/blocksync/verification.md b/spec/blocksync/verification.md index 3a8146122..8629d7491 100644 --- a/spec/blocksync/verification.md +++ b/spec/blocksync/verification.md @@ -51,10 +51,10 @@ If we can trust this initial state at height H, we can use this fact to eliminat ### Verifying blocks past the trusted state +block diagram -![Block overview](img/bc-reactor-blocks.png) -The [diagram](#Block_overview) shows all blocks at play when verifying block at height ` H + 1` - `newBlock`, where at height `H` we have the trusted block. +The diagram above shows all blocks at play when verifying block at height ` H + 1` - `newBlock`, where at height `H` we have the trusted block. At a high level, the verification algorithm is represented by the code below.