franjoespejo

I have the same issue, would make it easier to have access to the actual values specially as a beginner

I'd go for 2 yep, futures is not a hard concept to learn. moving operations elsewhere helps me

Thanks for checking in detail. Regarding UX, IMO once the verifying w3s is accepted, the pubkeys endpoint can send the verifying options, but meanwhile the options can be set in...

> There is no standard to set this on the validator client other than the keymanager api to manage remote signers or what are you referencing? The file config Nimbus...

> so this is limited to local blocks for now? we can't proof this in case of blinded block but I see you have another PR open that seems to...

I think It doesnt have access to the tx list but a hash instead, and the rest info remains. Pls check: [BlindedBlock](https://github.com/ethereum/beacon-APIs/blob/02d595daf39943430f54aa978f88a5c50d957e64/types/bellatrix/block.yaml#L77), it drives to [ExecutionPayloadCommon](https://github.com/ethereum/beacon-APIs/blob/02d595daf39943430f54aa978f88a5c50d957e64/types/bellatrix/execution_payload.yaml#L2 ) For the w3s...

Right, that would be the correct path. Looking at the nimbus code it seems they use it as a kind of selector and map execution_payload-execution_payload_header.

Thanks for checking in detail. Although that won't be the default option, it would be great to have it. It would let us to work with Teku vc seamlessly since...

Yes, that's for when a url is provided and would be an alternative to using keymanager APIs. For more context, The w3s url with the pubkeys of the validators that...