Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misconfigured sequencer forwarding #86

Open
klkvr opened this issue Oct 22, 2024 · 1 comment
Open

Misconfigured sequencer forwarding #86

klkvr opened this issue Oct 22, 2024 · 1 comment

Comments

@klkvr
Copy link
Contributor

klkvr commented Oct 22, 2024

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:

"--rollup.sequencerhttp={0}".format(sequencer_context.beacon_http_url)

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?

@tynes
Copy link

tynes commented Nov 22, 2024

This should definitely be pointing to the sequencer's EL client

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants