This is our Firehose instrumented fork of ledgerwatch/erigon repository. In this README, you will find instructions about how to work with this repository.
The tooling and other instructions expect the following project structure, it's easier to work with the Firehose fork when you use the same names and settings.
cd ~/work
git clone --branch="firehose-v2" git@github.com:graphprotocol/erigon.git
cd erigon
git remote rename origin sf
git remote add origin https://github.com/ledgerwatch/erigon.git
git fetch origin
For the best result when working with this repository and the scripts it contains:
- The remote
sfexists on main module and points togit@github.com:graphprotocol/erigon.git - The remote
originexists on main module and points to https://github.com/ledgerwatch/erigon.git
To install Erigon, run the below command
go install ./cmd/erigon
Battlefield requires geth and Erigon for the test. Clone the battlefield repo, install the clients(geth and Erigon) and run the below command to run the test
cd battlefield-ethereum
./bin/compare_vs_oracle.sh erigon
Erigon can be used as an Execution Layer (EL) for Consensus Layer clients (CL). Default configuration is OK.
If your CL client is on a different device, add --authrpc.addr 0.0.0.0 (Engine API listens on localhost by default) as well as --authrpc.vhosts .
Starting Erigon for goerli chain
erigon --datadir=<path_to_datadir> --firehose-enabled --chain=goerli --externalcl --private.api.addr=localhost:9090 --http.api=eth,erigon,web3,net,debug,trace,txpool,parity
In order to establish a secure connection between the Consensus Layer and the Execution Layer, a JWT secret key is automatically generated.
The JWT secret key will be present in the datadir by default under the name of jwt.hex. This piece of info needs to be specified in the Consensus Layer as well in order to establish connection successfully.
Once Erigon is running, you need to point your CL client to :8551, where is either localhost or the IP address of the device running Erigon, and also point to the JWT secret path created by Erigon.
Starting lighthouse for CL
lighthouse bn --network goerli --execution-endpoint http://localhost:8551 --execution-jwt <path_to_datadir>/jwt.hex --disable-deposit-contract-sync --datadir=/datadir/lighthouse --checkpoint-sync-url https://beaconstate-goerli.chainsafe.io --http
Firehose support stdin reader which we can use with Erigon instrumented client. Clone the firehose-ethereum repo and run the below command to start the instrumented client with Firehose:
cd firehose-ethereum
erigon --datadir=<path_to_datadir> --firehose-enabled --chain=goerli --externalcl --private.api.addr=localhost:9090 --http.api=eth,erigon,web3,net,debug,trace,txpool,parity $@ 2> /datadir/erigon/logs/erigon.log 1> >(./devel/standard-stdin/start.sh -c 2> /datadir/erigon/logs/firehose.log)