Conversation
|
Teku bootnode is: And I've set |
We're also using |
## Issue Addressed NA ## Proposed Changes Adds the configuration for the upcoming merge of the Ropsten network, as per: eth-clients/merge-testnets#9 Use the Ropsten network with: `lighthouse --network ropsten` ## Additional Info This is still a work-in-progress. We should wait for the eth-clients/merge-testnets PR to be approved before merging this into our `unstable`.
This PR adds the config files required by CL clients to instrument genesis. A summary of the chain configs are below:
16539228000x80000069100012500750435317567657135340x6f22fFbC56eFF051aECF839396DD1eD9aD6BBA9D(Same deposit contract code as mainnet)Values such as
ETH1_FOLLOW_DISTANCEwere left unchanged compared to other testnets.Once the PR has been merged, the client teams can be expected to receive mnemonics for their genesis validators. It'd be great if once the client teams have setup their bootnodes, if we could increase the bootnode list.