vc: request stateless gloas block production

[KaloyanTanev]

From the gloas fork, block production moves to produceBlockV4, whose include_payload parameter 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:

• Lodestar: --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.
• Prysm: --stateless. Off by default and only auto-forced on with multiple beacon nodes, so it is set explicitly here.
• Nimbus: no flag exists — it requests stateless only with >1 beacon node and cannot be overridden. Documented in nimbus/run.sh as a known gap (complete produceBlockV4 roundtrip status-im/nimbus-eth2#9084).
• Teku: does not yet implement produceBlockV4 on the validator client, so it cannot propose gloas blocks behind charon today. Documented in compose-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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[OisinKyne]

I worry should we be doing something in charon overriding proxying requests for operators that don't run in cdvn and maybe thus miss these flags?