stop using deprecated /eth/v1/beacon/blocks / publishBlock(V1) beacon API endpoint #7438
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.
https://ethereum.github.io/beacon-APIs/#/Beacon/publishBlock is deprecated with support disappearing likely across much of the ecosystem sometime after Fusaka forks on mainnet.
https://ethereum.github.io/beacon-APIs/#/Beacon/publishBlockV2 supports at least all the forks the non-V2 version does, even if one wants to use the VC in a pre-Electra network. Furthermore, none of the officially supported networks of Nimbus even involve producing pre-Pectra blocks anymore, so for those networks (Ethereum mainnet, Hoodi, Holesky, Sepolia, Gnosis mainnet, Chiado) it's already unused code.
One maintenance issue is that each time a hardfork is added, it adds 3 different places which have to be adjusted, which is why I'm looking at this while adding Glamsterdam.