2019-04-05 15:10:34 +00:00
|
|
|
# Syncing commands
|
2019-05-07 21:21:08 +00:00
|
|
|
These commands are used to sync raw Ethereum data into Postgres, with varying levels of data granularity.
|
2019-04-05 15:10:34 +00:00
|
|
|
|
2019-05-01 06:02:30 +00:00
|
|
|
## headerSync
|
2019-05-07 21:21:08 +00:00
|
|
|
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.
|
2019-05-13 21:29:06 +00:00
|
|
|
- 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.
|
2019-05-07 21:21:08 +00:00
|
|
|
|
2019-05-13 20:52:17 +00:00
|
|
|
#### Usage
|
|
|
|
|
- Run: `./vulcanizedb headerSync --config <config.toml> --starting-block-number <block-number>`
|
|
|
|
|
- The config file must be formatted as follows, and should contain an ipc path to a running Ethereum node:
|
|
|
|
|
```toml
|
|
|
|
|
[database]
|
|
|
|
|
name = "vulcanize_public"
|
|
|
|
|
hostname = "localhost"
|
|
|
|
|
user = "vulcanize"
|
|
|
|
|
password = "vulcanize"
|
|
|
|
|
port = 5432
|
|
|
|
|
|
|
|
|
|
[client]
|
|
|
|
|
ipcPath = <path to a running Ethereum node>
|
|
|
|
|
```
|
|
|
|
|
- Alternatively, the ipc path can be passed as a flag instead `--client-ipcPath`.
|
