From 622ea44a6f5542a20f04ae9ec3d7941dbbaf6fe2 Mon Sep 17 00:00:00 2001 From: Elizabeth Engelman Date: Mon, 13 May 2019 16:29:06 -0500 Subject: [PATCH] Mention reorgs in data-sync documentation --- documentation/data-syncing.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/documentation/data-syncing.md b/documentation/data-syncing.md index 99564540..52785ba5 100644 --- a/documentation/data-syncing.md +++ b/documentation/data-syncing.md @@ -5,7 +5,10 @@ These commands are used to sync raw Ethereum data into Postgres, with varying le Syncs block headers from a running Ethereum node into the VulcanizeDB table `headers`. - Queries the Ethereum node using RPC calls. - Validates headers from the last 15 blocks to ensure that data is up to date. -- Useful when you want a minimal baseline from which to track targeted data on the blockchain (e.g. individual smart contract storage values or event logs). +- Useful when you want a minimal baseline from which to track targeted data on the blockchain (e.g. individual smart +contract storage values or event logs). +- Handles chain reorgs by [validating the most recent blocks' hashes](../pkg/history/header_validator.go). If the hash is +different from what we have already stored in the database, the header record will be updated. #### Usage - Run: `./vulcanizedb headerSync --config --starting-block-number ` @@ -29,6 +32,8 @@ Syncs blocks, transactions, receipts and logs from a running Ethereum node into - Queries the Ethereum node using RPC calls. - Validates headers from the last 15 blocks to ensure that data is up to date. - Useful when you want to maintain a broad cache of what's happening on the blockchain. +- Handles chain reorgs by [validating the most recent blocks' hashes](../pkg/history/header_validator.go). If the hash is +different from what we have already stored in the database, the header record will be updated. #### Usage - Run `./vulcanizedb fullSync --config --starting-block-number `