[Tracking] - Prysm V4

[terencechain]

This PR tracks features to be included for the Prysm V4 release. Prysm V4 will target the Capella/Shanghai release and it's a hard fork / non-backward compatible release. We can divide Prysm V4 under the following sections and todos. Feel free to add anything as you see fit

Core consensus

• Process withdrawal and process new bls-to-exec changes
• Process historical batches

P2P

• Gossip and validation for the new new bls-to-exec changes

Beacon API

• Capella versioned beacon block and beacons state requests
• Withdrawal related request
• Historical batches related request

Sync

• Backfilling of beacon block for weak subjectivity sync

Builder / MEV-boost

• Block construction is supported through the new builder API for Capella

Prysmctl

• Node operator can sign and submit bls-to-exec changes

Web3Signer

• Web3signer Capella support

🦉

[james-prysm]

Should we decom the old prysm remote signer as part of v4?
#11700

[potuz]

Do we really want to have this a major release? It's only a few months from the merge and we will have a free pass for breaking changes in the APIs?

[james-prysm]

if there's time, fully deprecating some unused grpc endpoints for webui would be good.

[rkapka]

• Deprecate/remove removed/deprecated endpoints of Beacon APIs

[rkapka]

• Remove --interop-genesis-state flag, it's broken. We should use --genesis-state instead

[potuz]

Leaving here what I would personally want before code freeze for mainnet:

• Reorg late blocks
• Forkchoice changes and removal of flags.

[james-prysm]

• new event stream type payload attribute - SSE for payload attributes ethereum/beacon-APIs#305