-
Notifications
You must be signed in to change notification settings - Fork 2
feat: support directly forward transactions to sequencer #189
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added comment inline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add an e2e test for this using the test framework. See example provided:
rollup-node/crates/node/tests/e2e.rs
Lines 94 to 95 in 1ffce34
#[tokio::test] | |
async fn can_sequence_and_gossip_blocks() { |
Sure, let me do that. |
Thanks, I think you'll need to set |
Counterpart of l2geth scroll-tech/go-ethereum#1208.
Related Reth PR: scroll-tech/reth#265
Added a new flags on NetworkArgs.
network.sequencer-url
: This will be passed toScrollEthApiBuilder
, If not None, Reth will forward transactions to sequencer's RPC directly.