cerc-io/ipld-eth-server
17
0
Fork 1
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 37 Wiki Activity
e033eabc28
ipld-eth-server/vendor/github.com/vulcanize/eth-block-extractor
History
Ian Norden bc59aa4ed6 readme additions and vendor updates
2019-12-02 13:24:46 -06:00
..
cmd readme additions and vendor updates 2019-12-02 13:24:46 -06:00
environments readme additions and vendor updates 2019-12-02 13:24:46 -06:00
pkg readme additions and vendor updates 2019-12-02 13:24:46 -06:00
test_helpers readme additions and vendor updates 2019-12-02 13:24:46 -06:00
.gitignore readme additions and vendor updates 2019-12-02 13:24:46 -06:00
.travis.yml readme additions and vendor updates 2019-12-02 13:24:46 -06:00
LICENSE readme additions and vendor updates 2019-12-02 13:24:46 -06:00
main.go readme additions and vendor updates 2019-12-02 13:24:46 -06:00
Makefile readme additions and vendor updates 2019-12-02 13:24:46 -06:00
package.json readme additions and vendor updates 2019-12-02 13:24:46 -06:00
README.md readme additions and vendor updates 2019-12-02 13:24:46 -06:00

README.md

Eth Block Extractor

Build Status

Description

A VulcanizeDB transformer for creating IPLDs for Ethereum block data.

Dependencies

  • Go 1.9+
  • Postgres 10
  • Ethereum Node
  • IPFS
  • go-ipld-eth (Plugin enabling conversion of block headers to IPLDs in IPFS)

Installation

  1. Setup Postgres and an Ethereum node - see VulcanizeDB README.
  2. Sync VulcanizeDB to populate core block data (commands will read block data from VulcanizeDB to fetch and persist block RLP data).
  3. git clone git@github.com:vulcanize/eth-block-extractor.git

note: go get does not work for this project because need to run the (fixlibcrypto)[https://github.com/vulcanize/eth-block-extractor/blob/master/Makefile] command along with go build.

  1. Build: 
    make build

Configuration

  • To use a local Ethereum node, copy environments/public.toml.example to environments/public.toml and update the levelDbPath to the local node's levelDB filepath:
    • when using geth:
      • The LevelDB file is called chaindata.
      • The LevelDB file path is printed to the console when you start geth.
      • The default location is:
        • Mac: $HOME/Library/Ethereum
        • Linux: $HOME/.ethereum

Running the createIpldForBlockHeader command

  • This command creates an IPLD for the header of a single Ethereum block.
  • ./eth-block-extractor createIpldForBlockHeader --config <config.toml> --block-number <block-number>

Running the createIpldForBlockHeaders command

  • This command creates IPLDs for headers in a range of Ethereum blocks.
  • ./eth-block-extractor createIpldForBlockHeaders --config <config.toml> --starting-block-number <block-number> --ending-block-number <block-number>
  • Note: ending block number must be greater than starting block number.

Running the createIpldsForBlockTransactions command

  • This command creates IPLDs for transactions on an Ethereum block.
  • ./eth-block-extractor createIpldsForBlockTransactions --config <config.toml> --block-number <block-number>

Running the createIpldsForBlocksTransactions command

  • This command creates IPLDs for transactions on a range of Ethereum blocks.
  • ./eth-block-extractor createIpldsForBlocksTransactions --config <config.toml> --starting-block-number <block-number> --ending-block-number <block-number>
  • Note: ending block number must be greater than starting block number.

Running the createIpldsForBlockReceipts command

  • This command creates IPLDs for transaction receipts on an Ethereum block.
  • ./eth-block-extractor createIpldsForBlockReceipts --config <config.toml> --block-number <block-number>

Running the createIpldsForBlocksReceipts command

  • This command creates IPLDs for transaction receipts in a range of Ethereum blocks.
  • ./eth-block-extractor createIpldsForBlocksReceipts --config <config.toml> --starting-block-number <block-number> --ending-block-number <block-number>
  • Note: ending block number must be greater than starting block number.

Running the createIpldsForStateTrie command

  • Note: this command is very expensive in terms of time and memory. Probably only feasible to execute on an archive node for a narrow range of blocks.
  • This command creates IPLDs for state and storage trie nodes in a range of Ethereum blocks.
  • ./eth-block-extractor createIpldsForStateTrie --config <config.toml> --starting-block-number <block-number> --ending-block-number <block-number>
  • Note:
    • Optionally pass the --compute-state flag if not running an archive node (in which case state is pruned) - this will dynamically generate the state for each block by processing transactions.
    • Computing state requires beginning at the genesis block, so starting block number flag is ignored if not 0.
    • Ending block number must be greater than starting block number.

Running the tests

ginkgo -r