-
Notifications
You must be signed in to change notification settings - Fork 37
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:
1653922800
0x80000069
100012
500
750
43531756765713534
0x6f22fFbC56eFF051aECF839396DD1eD9aD6BBA9D
(Same deposit contract code as mainnet)Values such as
ETH1_FOLLOW_DISTANCE
were 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.