From 79476dead0341acb7c67e0be54b91e4271005b9a Mon Sep 17 00:00:00 2001 From: Jasmina Malicevic Date: Mon, 4 Jul 2022 14:55:02 +0200 Subject: [PATCH] minor --- spec/blocksync/readme.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/spec/blocksync/readme.md b/spec/blocksync/readme.md index 508b1d247..06782e99c 100644 --- a/spec/blocksync/readme.md +++ b/spec/blocksync/readme.md @@ -1,10 +1,11 @@ --- -order: +order: 1 parent: title: blocksync - order: + order: 3 --- +# Blocksync In a proof of work blockchain, syncing with the chain is the same process as staying up-to-date with the consensus: download blocks, and look for the one with the most total work. In proof-of-stake, the consensus process is more complex, as it involves rounds of communication between the nodes to determine what block should be committed next. Using this process to sync up with the blockchain from scratch can take a very long time. It's much faster to just download blocks and check the merkle tree of validators than to run the real-time consensus gossip protocol.