From 2079db7f0998e095c5ded56eadee09209d36843e Mon Sep 17 00:00:00 2001 From: Dmitriy Ryajov Date: Wed, 5 Jul 2023 08:58:03 -0600 Subject: [PATCH] fixed inconcistency in network flow --- design/metadata-overhead.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/metadata-overhead.md b/design/metadata-overhead.md index 0bdba62..8fd156e 100644 --- a/design/metadata-overhead.md +++ b/design/metadata-overhead.md @@ -207,6 +207,6 @@ Keeping support for hash based retrieval (content addressing) has two main advan 1. Once new peers have been discovered and connected, go to step 1.1.1 2. Once blocks are received from the remote nodes 1. The hashes are verified against the requested Merkle root and if they pass - 1. The block is persisted to the network + 1. The block is persisted to the repo/local store 2. The block hash (cid) and the Merkle proof are stored in the persisted Merkle tree 2. Otherwise, the block is discarded and the node that sent the incorrect block disconnected