Add support for engine_executeStatelessPayloadVX Engine RPCs

[Akagi201]

Describe the feature

engine_executeStatelessPayloadV1,engine_executeStatelessPayloadV2,engine_executeStatelessPayloadV3,engine_executeStatelessPayloadV4, engine RPC methods are already implemented in go-ethereum node, which is useful to execute a witness data to calculate block header fields.

Additional context

No response

[mattsse]

makes sense,

first we need a new rpc trait that defines the functions for this similar to:

reth/crates/rpc/rpc-api/src/engine.rs

Line 30 in 1b4048e

pub trait EngineApi<Engine: EngineTypes> {

[syjn99]

I'd love to take this

[mattsse]

assigned

[syjn99]

Hi @mattsse I'm investigating this work for a couple of hours, and I'd like to ask some questions for implementing this api.

• engine_executeStatelessPayloadVX methods were introduced in go-ethereum by karalabe, and I found that he also implemented new methods with suffix WithWitness(e.g. forkchoiceUpdatedWithWitnessVX). Do I have to implement all other methods like go-ethereum? If not, how can I test the whole flow of witness creation and consumption?
• IMO debug_execution_witness works as engine_executeStatelessPayloadVXs are expected to do so. Is this a good point to start this work? Related PRs:
  • feat(rpc): debug_executionWitness #9249
  • feat(witness): use block executor to execute block inside debug_execution_witness #11149

Thank you so much for your effort!

[mattsse]

I see, I think these are very similar to debug_executionWitness, I kinda prefer geth's naming here actually.

so for the first pr, let's define all of those, but only define the traits first.
implementation is more tricky and we can tackle this in followups

[syjn99]

Got it. Worried about my pr being too heavy for implementing all the things, but it will be fine if I only define the traits first. Thank you @mattsse

[syjn99]

gm @mattsse, I've just committed draft pr (#13016), and raised an issue to alloy for further implementation(alloy#1707).