-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Open
Copy link
Labels
custom-devnettoolsMetrics, prysm.sh and all the other toolingMetrics, prysm.sh and all the other tooling
Description
Describe the bug
When all beacon chains are shut down, the execution client cannot continue to produce blocks. One method is to obtain the latest EVM block from an existing execution client and use it to create a new beacon chain to continue running.
Using the prysmctl testnet generate-genesis flag --override-eth1data cannot set the correct latest information, which results in the beacon chain failing to start.
header, err := client.HeaderByNumber(ctx, big.NewInt(0)) - It should be necessary to fill in the latest execution payload header information.
Has this worked before in a previous version?
🔬 Minimal Reproduction
No response
Error
Platform(s)
No response
What version of Prysm are you running? (Which release)
develop branch
Anything else relevant (validator index / public key)?
No response
Metadata
Metadata
Assignees
Labels
custom-devnettoolsMetrics, prysm.sh and all the other toolingMetrics, prysm.sh and all the other tooling