Queuing on api if execution payload envelope is received first

[nflaig]

Is the submission process stateful, I.e. do you have to submit the payload to the same BN that you submit the beacon block to?

For my benefit - is the worry that, if you submit the block to one BN and then the execution payload to a second BN, that the second client might not have seen the block yet?

the BN needs the beacon block first to validate and process the execution payload however it's not required to submit both via the api

there will be a queue mechanism in clients for gossip as you can't be sure that you receive the beacon block before the execution payload there

From my comment here shane-moore/beacon-APIs#2 (comment)

[nflaig]

This is similar to #8811, would be good if we can use the same queuing mechanism for both

[twoeths]

as discussed, for block/envelope we want to go through UnknownBlockInput, not queueing in NetworkProcessor
do it via "network.search*" api
these apis are to be implemented later, see #9025

[nflaig]

not queueing in NetworkProcessordo it via "network.search*" api

does this mean we would just ignore the payload on gossip if it arrives first? I feel like at least for this simple case where the payload for the same slot arrives first, queuing makes sense