Make execution-endpoint required on the CLI

[zhiqiangxu]

Here's the command to run bn without execution-endpoint:

lighthouse bn --network sepolia  --http --allow-insecure-genesis-sync

Then I see lots of ExecutionLayerMissing errors:

Not sure whether it's the expected behaviour? But IMO if user didn't specify the execution-endpoint, these errors should not be shown since assumed.

[chong-he]

--execution-endpoint must be supplied for a beacon to sync; if it is not supplied, the beacon will complain about it because it can't sync

[zhiqiangxu]

--execution-endpoint must be supplied for a beacon to sync; if it is not supplied, the beacon will complain about it because it can't sync

Well, why not report an error and quit when started if --execution-endpoint must be supplied?

[michaelsproul]

Well, why not report an error and quit when started if --execution-endpoint must be supplied?

This is leftover from the pre-Merge era when we went from making --execution-endpoint optional, to making it mandatory. We could make the CLI flag .required(true) now that all networks have merged

[Parikalp-Bhardwaj]

Hi @michaelsproul , I was wondering if this issue is still open or if there's been any update on it?

[jimmygchen]

Completed in #5165 🎉