Skip to content

docs: Add rollup.sequencerhttp to node operation docs #865

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.

Sign up for GitHub

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

Merged
krofax merged 1 commit into from
Aug 28, 2024
Merged

docs: Add rollup.sequencerhttp to node operation docs #865

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions pages/builders/chain-operators/management/operations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,9 @@ If you do it this way, you won't have to wait until the transactions are written
If you already have peer to peer synchronization, add the new node to the `--p2p.static` list so it can synchronize.

### Start `op-geth` (using the same command line you used on the initial node)
<Callout type="warning">
**Important:** Make sure to configure the `--rollup.sequencerhttp` flag to point to your sequencer node. This HTTP endpoint is crucial because `op-geth` will route `eth_sendRawTransaction` calls to this URL. The OP Stack does not currently have a public mempool, so configuring this is required if you want your node to support transaction submission.
</Callout>

### Start `op-node` (using the same command line you used on the initial node)
</Steps>
Expand Down