vc: request stateless gloas block production - #489
Open
KaloyanTanev wants to merge 1 commit into
Open
KaloyanTanev wants to merge 1 commit into
KaloyanTanev wants to merge 1 commit into
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
From the gloas fork, block production moves to
produceBlockV4, whoseinclude_payloadparameter selects the stateless (payload-included) or stateful (payload-excluded) response form for self-built blocks. A distributed validator needs the stateless form: charon fans block production across nodes, so no single beacon node can be relied on to hold the cached envelope for the stateful flow.This sets each VC to request the stateless form where a lever exists:
--payloadLocal=false. Lodestar auto-selects stateless only when configured with >1 beacon node; behind charon (a single endpoint) it would default to stateful, so this sets it explicitly.--stateless. Off by default and only auto-forced on with multiple beacon nodes, so it is set explicitly here.nimbus/run.shas a known gap (complete produceBlockV4 roundtrip status-im/nimbus-eth2#9084).produceBlockV4on the validator client, so it cannot propose gloas blocks behind charon today. Documented incompose-vc.yml(Implement GET/eth/v1/validator/execution_payload_envelope/...Consensys-Incorporated/teku#11172).Note the VC image versions must be gloas-capable for these flags to be recognised; the flags are still pre-release and their names/defaults may change before the fork.
category: feature
ticket: none