Pre-requisites: git, go
Clone and build from source develop branch of Erigon
Execution layer conclusions
After starting the client, you will be able to interact with the client using the following ports:
localhost:8545: Web3 json rpc
localhost:8550: Engine json rpc
localhost:8551: Engine json rpc with json rpc authentication
jwt.hex in the repository where you ran the rpcdaemon: verification key for JWT authentication
Build Erigon Execution Layer
git clone https://github.com/ledgerwatch/erigon
cd erigon
make erigon rpcdaemon
cd ..
# Initialize database
./erigon/build/bin/erigon init \
--datadir=erigon-datadir genesis.json
# Run Erigon
./erigon/build/bin/erigon \
--datadir erigon-datadir \
--externalcl \
--networkid=1881 \
--authrpc.jwtsecret=/tmp/jwtsecret \
--http --http.api=engine,net,eth \
--bootnodes="TAKE IT FROM THE CARTENZ TESTNET REPOSITORY"
Before running the Node, we use the POSIX Nohup (No Hang UP) command which means (Do Not Close) a command in Linux systems that keeps the process running even after exiting the shell or terminal. Nohup prevents the process or job from receiving the SIGHUP (Signal Hang UP) signal. This is the signal sent to the process after closing or exiting the terminal.
nohup lodestar beacon \
--suggestedFeeRecipient "YOUR ADDRESS HERE" \
--execution.urls "http://127.0.0.1:8551" \
--jwt-secret /path/your/folder/jwt.hex \
--dataDir "/home/ubuntu/cartenz/data-2" \
--paramsFile "/home/ubuntu/cartenz/consensus/config.yaml" \
--genesisStateFile "/home/ubuntu/cartenz/consensus/genesis.ssz" \
--enr.ip 172.31.22.244 \
--rest.port 9599 \
--port 9001 \
--network.connectToDiscv5Bootnodes true \
--logLevel info \
--bootnodes="ADD YOUR ENR HERE AND ADDING MORE FROM THE CARTENZ TESTNET REPOSITORY" \
> /home/ubuntu/cartenz/logs/beacon_2.log &
Building a Staker To Be Good Validator
Visit the Staking Website and Select Deposit and Make a Deposit with Command:
// Example From Deposit
deposit new-mnemonic --num_validators 200 --eth1_withdrawal_address 0x9adddA86C9479C45bD145BBa9FC28146FdF46C83
# Example Output Mnemonic:
"vibrant refuse observe flag shy depth disagree proud race angle vote picnic fancy renew museum bonus arena people thumb there atom tuna abstract negative"
48-72hours
this cannot be an actual reference time. The sync process is very long and can take up to 48-72 hours. Sync speed depends on your internet speed and storage device write speed. Because data is stored in blocks and linked together, corruption in a single block can corrupt the entire data chain