Right now for all execution clients sequencer URL for forwarding is configured as sequencer_context.beacon_http_url where sequencer_context is sequencer's CL context, thus beacon_http_url is sequencer's consensus client RPC:

Is this intended? In Reth, if this parameter is configured, we forward sendRawTransaction requests directly. I believe that those can't be handled by op-node, so I'd expect this to be configured with sequencer's EL RPC?