chore(pectra): Use pectra devnet-4 compatible geth/prysm/mev-boost-relay #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to use the pectra branches of prysm and geth to build the correct genesis blocks. Currently their branches support devnet-4, which was also the version used for the "mekong" testnet that was active over devcon.
Unfortunately geth development is happening at https://github.com/lightclient/go-ethereum/tree/prague-devnet-4 so we have to use a
replace
directive ingo.mod
to point to his fork until it's merged.However when using the proper binaries, I was able to run the pectra chain in the playground! (I didn't even bother trying rbuilder since we're on reth 1.1.1 which isn't at the right devnet level).
Aside: I had to raise the genesis delay as lighthouse only logs genesis block hash differences if the genesis timestamp hasn't happened yet, and 5s wasn't long enough to get it to log.
Versions used:
These versions were pulled from the EF devops mekong configs:
https://github.com/ethpandaops/mekong-devnets/blob/master/ansible/inventories/devnet-0/group_vars/all/images.yaml