forked from cerc-io/ipld-eth-server
Extract price feed contract addresses to config
This commit is contained in:
@@ -29,7 +29,8 @@ Vulcanize DB is a set of tools that make it easier for developers to write appli
|
||||
|
||||
## Configuration
|
||||
- To use a local Ethereum node, copy `environments/public.toml.example` to
|
||||
`environments/public.toml` and update the `ipcPath` and `levelDbPath`.
|
||||
`environments/public.toml` and update the `ipcPath`, `levelDbPath`,
|
||||
`pipContractAddress`, `pepContractAddress`, and `repContractAddress`.
|
||||
- `ipcPath` should match the local node's IPC filepath:
|
||||
- when using geth:
|
||||
- The IPC file is called `geth.ipc`.
|
||||
@@ -51,7 +52,10 @@ Vulcanize DB is a set of tools that make it easier for developers to write appli
|
||||
- Linux: `$HOME/.ethereum/geth/chaindata`
|
||||
- `levelDbPath` is irrelevant (and `coldImport` is currently unavailable) if only running parity.
|
||||
|
||||
- See `environments/infura.toml` to configure commands to run against infura, if a local node is unavailable.
|
||||
- `pepContractAddress`, `pipContractAddress`, and `repContractAddress` should match that medianizer
|
||||
addresses for each pair on the chain you're tracking. See https://makerdao.com/feeds/
|
||||
|
||||
- See `environments/infura.toml` to configure commands to run against infura, if a local node is unavailable
|
||||
- Copy `environments/local.toml.example` to `environments/local.toml` to configure commands to run against a local node such as [Ganache](https://truffleframework.com/ganache) or [ganache-cli](https://github.com/trufflesuite/ganache-clihttps://github.com/trufflesuite/ganache-cli).
|
||||
|
||||
## Start syncing with postgres
|
||||
@@ -75,7 +79,7 @@ Sync VulcanizeDB from the LevelDB underlying a Geth node.
|
||||
Syncs VulcanizeDB with the configured Ethereum node, populating only block headers.
|
||||
This command is useful when you want a minimal baseline from which to track targeted data on the blockchain (e.g. individual smart contract storage values).
|
||||
1. Start Ethereum node
|
||||
2. In a separate terminal start VulcanizeDB:
|
||||
1. In a separate terminal start VulcanizeDB:
|
||||
- `./vulcanizedb lightSync --config <config.toml> --starting-block-number <block-number>`
|
||||
|
||||
## Backfill Auction event logs from light sync
|
||||
@@ -87,6 +91,12 @@ _Since auction contracts have not yet been deployed, this command will need to b
|
||||
1. Start Ethereum node
|
||||
1. In a separate terminal run the backfill command:
|
||||
- `./vulcanizedb backfillAuctionLogs --config <config.toml>`
|
||||
|
||||
## Sync in light mode with MakerDAO price feeds
|
||||
Sync VulcanizeDB with the configured Ethereum node, populating block headers as well as price feeds for MKR/USD, ETH/USD, and REP/USD.
|
||||
1. Start Ethereum node
|
||||
1. In a separate terminal window start VulcanizeDB
|
||||
- `./vulcanizedb syncPriceFeeds --config <config.toml> --starting-block-number <block-number>`
|
||||
|
||||
## Start full environment in docker by single command
|
||||
|
||||
|
||||
Reference in New Issue
Block a user